Re: Cocoon2 Design

[Philipp Meier <bi...@o-matic.net>]

On Mon, Jun 05, 2000 at 08:35:39PM +0200, Stefano Mazzocchi wrote:

> Neeme Praks wrote:
> > 
> > > -----Original Message-----
> > > From: Stefano Mazzocchi [mailto:stefano@apache.org]
> > > Sent: Friday, June 02, 2000 4:31 PM
> > >
> > > > Actually, how well is supported the "referral" feature:
> > > together with
> > > > the POST data the browser also sends the URL of the original page
> > > > (poster)?
> > >
> > > You mean to do sessions? Sorry, I need a better example here to
> > > understand what you mean.
> > 
> > I mean the that when browser requests a page, it also sends the URL of
> > the "referring" page that linked to the page being requested.
> > Example with GET:
> > ---- <page1.html> ----
> > <a href='page2.html'>Click here!</a>
> > ---- </page1.html> ----
> > 
> > So, when the user clicks on the link, the browser send the request for
> > "page2.html" and includes the URL ("page1.html") of the referring page.
> > If I remember correctly, it is included in HTTP headers?
> 
> I think so, yes, but I'm not sure. Is this a standard requirement?

No, as far as I know this behavior is completly optional. But the
desired behavior can be implemented in the web application with some
state machine design. Imagine the client would always call the same
base url (only with different query parameters) -- if you maintain the
state of the application on the server side, you can easily send 
whichever page you like to the client.

happy hacking,
	-billy.

-- 
Philipp Meier                              o-matic GmbH
Geschäftsführer                  Pfarrer-Weiß-Weg 16-18
Tel.: +49-(0)700-66284236                     89077 Ulm