External SHA hashes instead? (was: Re: Content length, EOF -- ways to resolve whether we received everything)

[Sean Conner]

It was thus said that the Great Solderpunk once stated:
> It's true that frequent use of "the back button" or similar
> navigational strategies to get around Geminispace means that certain
> individual pages may be loaded several times within a browsing session
> (one might go back and forth between a page listing entries in a gemlog
> and those individual entries), and that can be a little wasteful.
> Smarter navigation tools (like AV-98's "tours") can reduce this waste,
> but it's also easily fixed by clients doing something simple like
> keeping the 5 or 10 most recently visited pages cached in memory, with
> cached pages expiring after 10 minutes or so (AV-98 does this, although
> I don't think I've done a release since adding it).  Clients doing this
> would obviously have problems with content which updated more frequently
> than every 10 minutes, but that kind of content is - and I would argue
> *should* be - very rare in Geminispace.  Apps are the one obvious place
> where this strategy might fail, which is perhaps yet another argument in
> favour of having different clients optimised for reading and for apps.

  For my gopher client, I cache files that are fetched for the session. 
They're stored to disk, and when I quit out of the gopher client, the files
are deleted.  There is an option to reload an already loaded page, but I
don't think I use that all that often.

  -spc