On Wednesday, 13. September 2006 13:17, [EMAIL PROTECTED] wrote: > Is the Cache::Cache stuff in there for us to roll our own caching of > html pages or does Axkit2 have that inbuilt?
AxKit2 apps are not epected to do any wholesale caching like AxKit1 did. Large scale AxKit1 users usually put a squid as caching reverse proxy in front of AxKit1 anyway, and that approach is recommended if you need this kind of allround caching. The cachecache plugin is meant for situations when you find out that some step in your application is really expensive (an example is image scaling in demo/gallery) so you selectively cache only those parts that are actually slow. Be aware that we may change the caching API at some time in the future, baud isn't too happy with cachecache as it is now. On the other hand, since we have that flexible plugin system, if you are happy with cachecache, no one will stop you from using it from now on until eternity ;) Another strategy to improve performance is to do some processing at application startup. Since AxKit2 is a single-process server, you can easily parse stylesheets or do other expensive tasks before requests are coming in. By the way: serving static content is extremely fast in AxKit2. C-based servers probably beat it, but no one serves files faster in pure perl. -- CU Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
