On Mon, 15 May 2000, Jamie wrote:
> 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.
That's the traditional way of doing it, but it does mean that sablotron
would have to publish the tree interface to the outside world. I don't
know that there's a huge value in that.
