[11548] in www-talk@info.cern.ch
Re: Enforce reloading of page when using the back-button
daemon@ATHENA.MIT.EDU (Reinier Post)
Mon Mar 20 09:56:41 2000
Date: Fri, 17 Mar 2000 03:31:49 -0500 (EST)
Old-X-Envelope-From: www-talk-request@tux.w3.org Fri Mar 17 03:31:48 2000
Message-Id: <20000317093138.J3258@win.tue.nl>
From: Reinier Post <rp@win.tue.nl>
To: Arjun Ray <aray@q2.net>, www-talk@w3.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.LNX.4.10.10003082058500.12107-100000@mail.q2.net>; from Arjun Ray on Wed, Mar 08, 2000 at 09:19:15PM -0500
Old-X-Envelope-To: www-talk
Resent-From: gerald@w3.org
Resent-To: www-talk@w3.org
On Wed, Mar 08, 2000 at 09:19:15PM -0500, Arjun Ray wrote:
> 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.
It's "the user" who is the problem here, thefactor the browser has
no control over. Users can be replaced with others, as in this case,
without the browser realizing.
But if the developer gets to pick the browser, a Javascript solution
will suffice.
--
Reinier
