Hi,
Is there any reason for using XMLString in some places while not using it
in others ?
In particular, I noticed XMLString is used for char data, PI data, and few
other places, but it is not used for attribute values.
Another question is related with XMLString.toString(). It seems it allways
calls new String(), I think it would help to cache the conversion result,
in case someone will call this method later.
IMHO it would be much better if XMLString would be used consistently in
all places where a String is used, and maybe enhanced with few utility
methods that could avoid creating the String in common processing
( like compare with a String, etc ). This will allow XNI to operate
without producing any garbage at all - the upper layer will of course
generate the garbage for the elements/data it needs to convert to strings.
It's not that important for element and attribute names, as it is possible
to reuse the Strings, but at least attribute values should be treated the
same as char data.
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
