Re: Server control over history?

• Mail folder: WWW Talk Jan 94-present
• Next message: Kevin Altis: "SGML parsing, moving between formats"
• Previous message: M. Abul Masrur: "Message sent from mmasrur."
• Maybe in reply to: Frederick G.M. Roeber: "Re: Server control over history?"
• Reply: rodw@cbl.leeds.ac.uk: "Re: Server control over history?"

Errors-To: listmaster@www0.cern.ch
Date: Tue, 15 Feb 1994 17:24:29 --100
Message-id: <9402151611.AA13602@manuel.hpl.hp.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: dsr@hplb.hpl.hp.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Dave_Raggett <dsr@hplb.hpl.hp.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Server control over history?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 808

>> Another common case occurs with fill-out forms. Keeping a
>> history of the successive stages of filling out a form, and
>> the updates to that form by the server is of dubious value
>> (it would only make sense in the context of
>> a multi-level UNDO mechanism).

> Exactly---but this sort of automatic unlimited UNDO capability is a  
> wonderful thing for increasing interactivity.  The higher bandwidth  
> of interaction you want to achieve, the more useful it becomes.

But, how do you get the database at the other end to roll back
in sync with the browser. At the very least the browser would have
to send a message to the server to roll-back each step. This is well
outside the current HTTP/fill-out forms mechanism. Worse, I can't
see how its possible to roll-back the state in all cases.

Dave