Return-Path: 
 <cocoon-dev-return-12173-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 71746 invoked by uid 500); 4 Apr 2001 21:28:39 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 71708 invoked from network); 4 Apr 2001 21:28:36 -0000
Message-ID: <3ACB9167.8B97598C@apache.org>
Date: Wed, 04 Apr 2001 17:25:59 -0400
From: Berin Loritsch <bloritsch@apache.org>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: question on getLogger()
References: <Pine.LNX.4.30.0104041504100.10189-100000@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Donald Ball wrote:
> 
> On Wed, 4 Apr 2001, Giacomo Pati wrote:
> 
> > > On Wed, 4 Apr 2001, Giacomo Pati wrote:
> > >
> > > > My position is that caching the serializers output is less important. It
> > > > can be easily done by a caching proxy infront of C2. The only thing is
> > > > that some components will have to set HTTP headers to make the output
> > > > proxy friendly. The Readers are already doing so. We've used proxies
> > > > with amazing performance gain (at the client side) of Readers output and
> > > > especially from images produced by the SVGSerializers.
> > >
> > > that's a very good point. on what variables can you have the proxy vary
> > > its cache?
> >
> > I don't think I get what you mean. The Reader components we have uses
> > parameters like
> >
> >   <param name="expires" value="100"/>
> >
> > which means for the proxy which is requesting the resource that it at
> > least can proxy it for 100 seconds. Another thing is if the proxy (or
> > the client browser) is asking with a header "if-modified-since" then the
> > Readers will response with a HTTP-Code without producing the resource if
> > it is not modified since.
> 
> but the proxy needs to know if the response varies on the user agent, or
> request variables, or http request type, or cookie values, etc.... right?

For more info on what a proxy can and can't do, I'd suggest reading up on
Squid Proxy server (you can find a link on www.freshmeat.net).  I friend
of mine set this up at our church to force all computer access to the net
through the proxy.  It was mainly done for two purposes: make sure
inappropriate sites are blocked and logged, and ease administration.
You can use many settings to cache access to the net for the performance
gain that Giacomo was talking about.

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