XOM API for Processing XML with Java

[John Cowan <cowan AT ccil.org>]

Elliotte Harold scripsit:

> However the problem with this solution is that it adds another 4 bytes 
> per element to XOM's memory footprint, and I don't think that's a price 
> I'm willing to pay here. I'll see if I can fix the problem some other 
> way that has less of a downside.

Most apps retreive not only the next child but from the same parent
element.  You could therefore keep global (or thread-local) state
of lastParent and lastPosition.  However, experiment would be needed
to see if the required synchronization or thread-local variable would
be expensive enough to make the optimization pointless.

-- 
John Cowan      cowan AT ccil.org        http://www.reutershealth.com
        "Not to know The Smiths is not to know K.X.U."  --K.X.U.