I am not
familiar with xsp (anymore). I use jx all the time (with flow). It is by default
not cached, though you can arrange this via flow.
So, how many
User-Agent's do you expect? Do you expect a have load? I think regardless the
User-Agent you will have quite some parts of the request in common. Make these
cached!! Certainly, cocoon is very flexible and cool, but I think you really
should use the caching strategies provided by cocoon.
Running cocoon live
is very well posible with a high load (I have been able to serve 2000 pages/sec
on my local pc with caching), but not without caching! Try out solex (http://www.hippocms.org/display/CMS/Solex)
or Charles (not free) to keep an eye on your performance. Dont try to make
your app performing on the end, start right away.
Regards
Ard
--
Hippo
Oosteinde 11
1017WT Amsterdam
The
Netherlands
Tel +31 (0)20
5224466
-------------------------------------------------------------
[EMAIL PROTECTED]
/ http://www.hippo.nl
--------------------------------------------------------------
I'm working on a multi-publishing system for mobile devices. The same page will be published differently according to the User-Agent. Therefore, it's nearly useless to use caching in these conditions, especially if those pages are updated frequently.Actually, what is not clear for me is the relation there is between the fact that an XSP is a Poolable component (which means there is a pool of XSPs stored somewhere by Cocoon) and the fact that XSP are stored by Transient-store.I don't understand why I have to set some pool-max parameter for the <map:generator name="serverpages"> component and some maxobjects for the transient-store which handles previously loaded generators.Imagine I have a first request where some XSP is compiled and used to generate Page A.Now, imagine the same page A is requested again : will Cocoon load the previously generated XSP from the transient-store or from the pool of XSPs ?Regards,
2006/7/3, Ard Schrijvers <[EMAIL PROTECTED]>:I suppose default in cocoon it says:
<parameter name="use-store" value="true"/>
So yes, it does certainly make sence, because your xsls (I am not sure if they get compiled but I would guess they are) arent stored otherwise in the transient store.
Cocoon comes along with quite some nice caching already configured, so I think if you change things, you should either be certain about what and how you change it, or just trust the default configuration. Note that the xsl's (I think compiled thus) are being cached in transient store regardless the pipeline caching strategy!! So even in a noncaching pipeline, they are cached. But, I have never had a situation where I did not want this behavior, and I cannot imagine a situation where you would have a reason not to cache.
You can follow what is cached in the different stores via the StatusGenerator.
Regards Ard
--
Hippo
Oosteinde 11
1017WT Amsterdam
The Netherlands
Tel +31 (0)20 5224466
-------------------------------------------------------------
[EMAIL PROTECTED] / http://www.hippo.nl
--------------------------------------------------------------
Hello all,
I'm using Cocoon 2.1.8 with XSLTC.
I try to get the best performances from my configuration.
Does it make sense to use parameter <parameter name="use-store" value="true"/> when using XSLTC ?
Same question if I disable caching by using <map:pipe name="noncaching" src=""> ...
Regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
