XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

On Feb 1, 2005, at 8:46 PM, Elliotte Harold wrote:

> Wolfgang Hoschek wrote:
>
>
> > As an aside, if i remember it correctly, the BinaryXMLCodec 
> > deserializes in a more compact manner, somewhere around 4 memory 
> > bytes per file byte.
>
>
> Now how does it do that? If it's starting with the same XML document 
> and eventually arriving at the same XOM Document object, albeit with a 
> detour through binary XML, that's a bit surprising. Is it interning 
> strings the standard builder is not interning?

It's interning *all* strings (but not with String.intern(), but rather 
with a better application-level scheme). A large fraction of the binary 
data is essentially an array of unique string occurances, stored in 
compact form. Then there are byte level tokens identifying node types 
and compact byte-level integer indexes referring to the string table.

Beyond that, it also using the XOM Node copy constructors as much as as 
possible, to share more memory, faster object construction, and to 
avoid reverification of things that have already been verified before.