--On Monday, June 14, 2004 3:27 PM +0100 [EMAIL PROTECTED] wrote:
Should AxNoCache be on or off for a production server?
I think it depends on the situation.
Are you serving essentially static content? i.e. are changes to the content infrequent? If so, its probably useful. If your server is falling over from the load of re-generating the pages every time, it should help.
Is your content very dynamic? If so, it may be less useful. If you never serve the exact same content twice, caching the content is actually a waste of time.
If you're primarily doing a web-application (which is what I do with AxKit), you probably want caching off, because you may want the data source to be queried again, as there may be side effects generated by the act of viewing fetching a particular URL.
Either way, remember that the stylesheets themselves will still be compiled & cached. (And updated if they change).
If you're having performance problems with individual queries with caching off, turning it on won't improve the first query of each page. But it'll help with repeated queries. You may be able to improve the performance of the first query by re-writing your XSLT/XSP. For example, if your XML is large and you're doing a lot of searching through it in your XSLT, using xslt:key may vastly improve your performance.
-David Nolan Network Software Developer Computing Services Carnegie Mellon University
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
