On Fri, 6 Nov 2020 12:57:11 +0530 Sudipto 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't require any breaking changes, and a client that doesn't recognize the difference between codes 20 and 21 will still be fully compatible with a server that does. There can be different codes roughly representing different cache lifetimes. "PERMANENT" for things that should stick on the disk until the user (or user configured policy) removes them. "SESSION" for things that stick for the lifetime of a browsing session. A HTTP HEAD Last-Modified like solution also provides little advantage for the smaller documents people typically serve on Gemini. A lot of overhead exists in TLS negotiation, so one request is almost certainly better than two for small blog posts or articles. -- Philip -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201106/c453 1315/attachment.sig>
---
Previous in thread (6 of 55): 🗣️ Björn Wärmedal (bjorn.warmedal (a) gmail.com)
Next in thread (8 of 55): 🗣️ Philip Linde (linde.philip (a) gmail.com)