💾 Archived View for rawtext.club › ~sloum › geminilist › 003099.gmi captured on 2020-11-07 at 03:21:23. Gemini links have been rewritten to link to archived content

View Raw

More Information

-=-=-=-=-=-=-

<-- back to the mailing list

Caching and status codes

John Cowan cowan at ccil.org

Sat Nov 7 03:55:50 GMT 2020

- - - - - - - - - - - - - - - - - - - 

On Fri, Nov 6, 2020 at 10:48 PM bie <bie at 202x.moe> wrote:

This reduces gemini to a simple file sharing protocol and basically says
that dynamic content is out (unless only targeting advanced clients).

Here are my assumptions.

1) Clients are going to cache, like it or not. Some already do.

2) Servers are in the best position to say whether content is dynamic ornot. "Dynamic" in this case is not just CGI-generated; it's also staticfiles that change often. (I post a static file on the Web that isrecomputed every ten minutes by a cron job.)

3) If the server can communicate "don't cache this", the client can providea better UX.

Ultimately, I like the gemini protocol just the way it is (and wouldn'

be opposed to even a 1000 year feature freeze) but arbitrary caching by
clients kills a whole host of use-cases around generated and dynamic
responses.

That horse has sailed and that ship is out of the barn. "The world will goas it will, and not as you or I would have it."

John Cowan http://vrici.lojban.org/~cowan cowan at ccil.orgweirdo: When is R7RS coming out?Riastradh: As soon as the top is a beautiful golden brown and if youstick a toothpick in it, the toothpick comes out dry.-------------- next part --------------An HTML attachment was scrubbed...URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201106/b73ad739/attachment-0001.htm>