> > on the other hand, having the caching configured properly
> > would probably
> > solve the problem too.
>
> Wait, this last statement makes it sound like you are only interested
> in keeping the results cached to reduce load. If that is the case,
> use cocoon caching - it will automatically keep the result in
> memory and
> optionally write it out to disk/database as well. Caching
> will not keep
> a .pdf file anywhere - it remembers ("compiles" in docs is misnomer)
> the byte-stream for reuse if appropriate. I would highly
> reccomend against
> attempting to introduce your own file-based caching system
> when a good one
> is already in place.
>
> Hopefully, that's not what you meant by that.
I wonder if Cocoon (2.1?) handles Last-modified management?
So when the browser requests something, Cocoon can
(automatically or via custom actions) provide a Last-modified,
and the client then decides if he can use its cache.
I read that Cocoon handles Expires. But Expires and Last-modified
are different notions.
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
