Re: Server control over history?

Tony Sanders <sanders@BSDI.COM>
Errors-To: listmaster@www0.cern.ch
Date: Tue, 15 Feb 1994 18:03:46 --100
Message-id: <199402151659.KAA03437@austin.BSDI.COM>
Errors-To: listmaster@www0.cern.ch
Reply-To: sanders@BSDI.COM
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Tony Sanders <sanders@BSDI.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: 742
Dave_Raggett writes:
> Neal Holtz writes:
> > Is anyone else interested in having the server have some control over
> > a clients history list?
> > ... In these cases, you probably do not want to see these nodes put
> > on the history list.
> 
> I have been worrying about this too. For instance if you follow a thread

How about just having the browser use <A HREF="..." REV="Precedes">...</A>
and if the previous link matches the HREF then go "back", if not, continue
adding things to the history list like normal.

I believe that having servers directly messing with client history lists
is a can of worms that we really don't want to open.  Whatever happens
on the client end should be implied by generic hypertext operations.

--sanders