W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1995

Re: Improving If-Modified-Since

From: Albert Lunde <Albert-Lunde@nwu.edu>
Date: Tue, 15 Aug 1995 22:14:01 -0500 (CDT)
Message-Id: <199508160314.AA291592841@casbah.acns.nwu.edu>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
> > If the user requests a "Reload" operation, they are asking for a
> > new copy of the resource from its origin.
> We obviously have different opinions on what a "reload" should do.
> My interpretation of "reload" is to check everything on the page
> and retransfer any objects that have changed.

This is a case where it doesn't pay to be too clever.

If everything works perfectly, there is seldom a reason for
people to use "reload". The two cases I use it are when I have
a document that looks like it was corrupted by a transmission
error or when I have outside information that a document *has*
changed (usually because I'm editing it.)

In neither case do I want a local or remote cache be in the picture.

    Albert Lunde                      Albert-Lunde@nwu.edu
Received on Tuesday, 15 August 1995 20:15:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:14 UTC