On Mon, May 15, 2000 at 04:17:46PM +0200, Kaiserovi wrote:
> 3) I thought about your idea of a 'persistent Processor object' and I
> must say it does have several advantages. Thus a Processor would live
> longer than just one stylesheet application, and would have its own pool
> of ready-made trees, own processing options and registered handlers etc.
> There would possibly be one processor per thread (NOTE that Sablotron
> currently does not support multi-threading - would this work well with
> your project?).
What if you made the caching the responsibility of the application?
In some way shape or form, had the application hand sablotron a "ready made
tree" created from some place else that sablotron doesn't need to keep track
of. (Then the application can make decisions like "This stylesheet is used a
lot so lets keep it around") would that take away some of the burdons from
the sablotron library? I'm not a big object-fan, but it seems objects are an
ideal choice, either that or "file handle notion" of some sort.
Jamie
