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

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



> Regards,
> Elmar
> 
> -----Ursprüngliche Nachricht-----
> Von: Vadim Gritsenko [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 25. Juli 2002 18:27
> An: [EMAIL PROTECTED]
> Betreff: RE: caching strategy
> 
> 
> > From: Sternath Elmar [mailto:[EMAIL PROTECTED]]
> >
> > Hello,
> >
> > I wrote an application reading data from another application server
> and
> > sending requests to this application server which manipulate these
> data and
> > reread the manipulated data. All this is done inside one pipeline
> using
> > URLMatchers. CIncludeTransformer is used to concatenate multiple
input
> > streams. Reading and Re-Reading is exactly the same pipeline match.
As
> reading
> > of the data is time-consuming I only want to get data from the
server
> after a
> > manipulating request. Any suggestions for a caching strategy, maybe
by
> > extension of the CachingCIncludeTransformer??
> 
> If you include cocoon:/ uris, then they will be cached independently
> (IIRC). If you also use CachingCIncludeTransformer, then whole result
> will be cached too.
> 
> Vadim
> 
> 
> > Regards,
> > Elmar
> 
> 
> ---------------------------------------------------------------------
> 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]>
> 
> ---------------------------------------------------------------------
> 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]>



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

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