💾 Archived View for rawtext.club › ~sloum › geminilist › 003083.gmi captured on 2020-11-07 at 03:20:49. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Philip Linde linde.philip at gmail.com
Fri Nov 6 10:11:04 GMT 2020
- - - - - - - - - - - - - - - - - - -
On Fri, 6 Nov 2020 12:57:11 +0530Sudipto Mallick <smallick.dev at gmail.com> wrote:
But the problem is, where does the timestamp goes in the request and response?
I think that's the advantage of bie's suggested solution. It doesn'trequire any breaking changes, and a client that doesn't recognize thedifference between codes 20 and 21 will still be fully compatible witha server that does.
There can be different codes roughly representing different cachelifetimes. "PERMANENT" for things that should stick on the disk untilthe user (or user configured policy) removes them. "SESSION" for thingsthat stick for the lifetime of a browsing session.
A HTTP HEAD Last-Modified like solution also provides little advantagefor the smaller documents people typically serve on Gemini. A lot ofoverhead exists in TLS negotiation, so one request is almost certainlybetter than two for small blog posts or articles.
-- Philip-------------- next part --------------A non-text attachment was scrubbed...Name: not availableType: application/pgp-signatureSize: 488 bytesDesc: not availableURL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201106/c4531315/attachment.sig>