cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <ba...@webslingerZ.com>
Subject Re: AW: [C2] Sitemap Components, Content-Negotiation and Caching
Date Mon, 07 May 2001 16:20:37 GMT
On Mon, 7 May 2001, Carsten Ziegeler wrote:

> > > The Problem
> > > ===========
> > >
> > > Multiple sitemap components within a pipeline may consider multiple
> > > aspects ("dimensions") of a request. A HTTP server must/should tell
> > > the client (be it user agent or cache) which aspects the delivered
> > > data depends on. The means to tell this is the HTTP/1.1 "Vary:"
> > > header.
> > >
> > > However, there seems to be no mechanism in Cocoon 2 by which the
> > > components can set the "Vary:" header in a cooperative fashion to
> > > correctly reflect all considered aspects.
> >
> > naively speaking, i'd reckon that it'd be the job of the cache manager to
> > set the HTTP/1.1 Vary header. components can (and do, right?) tell the
> > cache manager what variables upon which they vary. i think right now it's
> > done on an ad hoc basis throughout the components. i reckon carsten would
> > know a bit better?
> >
> Yes, this is correct. Each component knows on which aspects it depends.
> So this component is currently responsible for setting the correct headers.
> For example the BrowserSelector sets the "Vary: User-Agent" header etc.
> If a component depends on other values it has to set them by itself. This
> is the only working solution right now.

but the components _do_ tell the cache manager what variables they vary
on, right? so it should be possible for the cache manager to take over
this job?

- donald


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message