On Mon, Oct 27, 2008 at 8:12 AM, vladimirn <nezaboravi@xxxxxxxxx> wrote: > > I have one simple question, actually i am interested in your point of view. > Is there any sense in caching xslt itself? If so, then why? If not, then > again why? :) > I think that there is no sense, and that xslt output should be cached. > What do you think? > > > Per Jessen wrote: > > > > vladimirn wrote: > > > >> i was wondering whats the best approach to do next. > >> I have an xml file delivered from service of my partner. On my web > >> server (windows) i have xslt files used for xml transformation. > >> Those files are getting bigger, so i have request to cash them and use > >> cashed. > > > > Your xslt files are source code, so why is there a need to cache them? > > > > > > /Per Jessen, Zürich > > > > > > -- > > PHP General Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > -- > View this message in context: > http://www.nabble.com/PHP-XSLT-caching-tp20173225p20186499.html > Sent from the PHP - General mailing list archive at Nabble.com. > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > I can see that caching the output would make sense, caching the source xslt files doesn't make any sense -- Bastien Cat, the other other white meat
