Re: [xslt] libxslt: xsl:include/import cache?
- From: Pete Ryland <pdr pdr cx>
- To: xslt gnome org
- Subject: Re: [xslt] libxslt: xsl:include/import cache?
- Date: Thu, 6 Dec 2001 00:20:21 +0000
On Wed, Dec 05, 2001 at 02:00:58PM -0500, Daniel Veillard wrote:
> On Wed, Dec 05, 2001 at 06:05:15PM +0000, Matt Sergeant wrote:
> > On Wed, 5 Dec 2001, Daniel Veillard wrote:
> > > On Wed, Dec 05, 2001 at 04:24:18PM +0000, Matt Sergeant wrote:
> > > > I've been thinking about this some, and I think it might be quite a
> > > > useful pattern for many people. So how about having a "document"
> > > > callback, which would be mutually exclusive with the current
> > > > "open/read/close" callbacks? It would just return a xmlDocPtr given
> > > > a URI following a successful match.
> > >
> > > So you grow up a pool of in-memory trees. How do you know when to
> > > free one of them ?
> > That's my problem, not yours.
> Okay, I was assuming you asked libxml to maintain that pool. This
> wasn't clear in your message. If it's not the case, simply design your
> own API on top of the existing file access one and the resolver hook.
Yep. FWIW, I do a similar thing in xmldb. Caching frequently-used xsl
templates does save a lot of time when you know beforehand that there's only
a few that need to be cached.
] [Thread Prev