> From: Sternath Elmar [mailto:[EMAIL PROTECTED]]
> 
> Hi Vadim,
> 
> thanks for your support. Caching works now for JSPs and also for
> CIncludeTransformer as long as I get my XML input from static xml
files.
> Unfortunately, I have to get my XML input via HTTP requests from a
remote
> server. In this case, these requests are always executed, caching does
not
> work. Do you have any idea how to solve this problem??

IIRC, remote server has to return "Last-Modified" header (see URLSource.
getInfos()). Otherwise, Cocoon will assume that content is not cacheable
(in accordance with http spec).

Vadim


> Thanks,
> Elmar
> 
> -----Ursprüngliche Nachricht-----
> Von: Vadim Gritsenko [mailto:[EMAIL PROTECTED]]
> Gesendet: Freitag, 26. Juli 2002 15:24
> An: [EMAIL PROTECTED]
> Betreff: RE: caching strategy
> 
> 
> > From: Sternath Elmar [mailto:[EMAIL PROTECTED]]
> >
> > Hi Vadim,
> >
> > thanks for your response. Just another, more detailed question now:
> > I have not
> > yet understood very well what I have to do to decide whether the
> > cached stuff
> > can be used or a new request to the back end server has to be sent
> > (depending
> > on whether a data manipulating request was done before or not).
> > Do I have to
> > mark the cached stuff somehow as 'dirty' as soon as a manipulating
> > request is
> > sent? Or do I have to keep track of the last request? And if so,
> > do you have a
> > suggestion how to do it??
> 
> Components decide for themselves whether whatever it does changed or
> not. Browse through user docs, for example:
> http://xml.apache.org/cocoon/userdocs/generators/file-generator.html:
> "Cacheable: yes - uses the last modification date of the xml document
> for validation".
> 
> For XSPs, see cacheable.xsp sample.
> 
> Vadim
> 
> 
...


---------------------------------------------------------------------
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]>

Reply via email to