[11522] in www-talk@info.cern.ch
Re: Enforce reloading of page when using the back-button
daemon@ATHENA.MIT.EDU (Grahame Grieve)
Wed Mar 8 21:58:52 2000
Date: Thu, 9 Mar 2000 13:43:34 +1000
Message-Id: <200003091343.AA2448294796@melb1.kestral.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: "Grahame Grieve " <grahame@melb1.kestral.com.au>
Reply-To: <grahame@melb1.kestral.com.au>
To: www-talk@w3.org
Resent-From: www-talk@w3.org
>History mechanisms and caches are different.
>In particular history mechanisms SHOULD NOT
>try to show a semantically transparent view
>of the current state of a resource. Rather,
>a history mechanism is meant to show exactly
>what the user saw at the time when the
>resource was retrieved.
>That's a *given* of browser functionality.
>An application that sees fit to demand
>petulantly that something be done about
>this, wasn't really for the web to begin with.
No petulance here. And you may be right, the
web may not support my application. But this
attitude runs contrary to accepted wisdom,
which is that the web is good for everything.
The http working group discussed allowing the
server to ask the browser not to honor the bit
above but chose not to. I would hope that you
understand why I wish they had allowed for it.
I guess we'll just have to wait for http-ng...
Grahame
