On Tue, Oct 03, 2000 at 11:38:35AM +0200, Kaiserovi wrote:
> Andreas,
>
> this issue has appeared several times on the list and I agree that it
> would improve the performance a lot in many cases. We simply haven't
> reached a satisfactory conclusion as to how to deal with the cache. One
> problem is that Sablotron may often be just a component of a larger
> system - wouldn't it be reasonable to provide hooks to let the system do
> the caching? If not, should the cache be processor-instance-specific or
> global? Should caching be transparent for the user or rather performed
> on demand?
We can also leave the caching in the control of the application.
What about an interface to preparse a XSL sheets. The function
should return a pointer to the internal structure. And then
a new function to pass this pointer to a processor. If
Sablotron is well structured this should not be a large problem ?
Andreas
