I don't know how easy it'd be to have the server figure out when to
re-render. are there existing caching mechanisms that could do this?

the java servlet could cache things too, of course, but then it'd have to
manage the cache (keep it under a certain size, etc).

James

-----Original Message-----
From: Earl Bingham [mailto:earl@xxxxxxxxx]
Sent: Monday, June 21, 1999 2:48 PM
To: xsl-list@xxxxxxxxxxxxxxxx
Subject: RE: XSL Optimizations




I can make the source available if people want it. Performance is quite good
as a result (no numbers though, sorry). It might be even better to cache the
rendering and only re-render as needed.

James

I'm curious your thoughts on caching the transformation mechanisms on a
system? Would it require specific java programming? Or would the web
server handle this explicityly?

Thanks,

Earl Bingham


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list