XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

On Aug 12, 2004, at 5:41 PM, Elliotte Rusty Harold wrote:

> I just don't see the problem here. The only reason you would ever care 
> about this is if for some strange reason you're creating thousands and 
> thousands of Builder objects, and that's not a plausible use case 
> because builders are reusable. If you want to parse documents in 
> parallel in separate threads, give every thread gets its own builder. 
> Problem solved.
>
> You seem to be proposing a very complex solution to a very easily 
> solved problem. Is there something more complicated here I'm not 
> seeing?

It's obvious for simple demo usage or for hard-wired designs where one 
can make assumptions about usage, and non-trivial if you have a 
framework where it's classes are decoupled and should not care about in 
which thread and in which environment they are being used. For example, 
think webservice in container with concurrent requests, with XML 
parsing usage decentralized in all sorts of corners of the framework. 
You are not in control when and where and how new threads are created, 
you just live in arbitrary contexts...

Anyway, the bottom line is that Builder reuse is often a lot more 
complicated than simply constructing a new Builder() in each 
method/class where one is required, and so they're not reused in 
practise, and so the performance penalty is indeed large. What do other 
folks think? What's their current practise? A new Builder everytime you 
need one? Curious...