On 11 Dec 2003 at 20:46, Robert Sanderson wrote:

> > > If so, then they can also have access to the parameters of the request
> > > they just sent, and we can ditch echoedRequest.  But I can't see how to do
> > > either without significant Javascript hackery.
> > The echoedRequest is needed to make the response self containing, which
> > allows easy navigation without much Javascript. Clients can do a lot
>
> Right. Ditto for the full URI in the response, not short names.
> Allowing one and not the other is not something that I could explain the
> reasoning behind.

Suppose you want to store some context information in a separate browser window.
When moving backward and forward in a web browser some context information like
the request parameters has to move along, but other information like the explain record
for a certain server may remain static during a session.

Theo