hi,

the whole Xalan-C XalanDOM classes are abstract and implemented for
example by the XalanSourceTree classes except XalanDOMString surely
because of performance.
But if the node data must be wrapped by an underlying in-memory
representation to XalanDOMString references, for example the conversion
from const XMLCh* to const XalanDOMString& in XercesParserLiaison done
by XercesDocumentBridge's XalanDOMStringPool, in worst case the data
must be copied each time to fit into the XalanDOMString vector model,
often there are many equal strings like names, etc. that can be cached
and reused, but double memory allocation or a cache lookup/string
compare overhead is always there.

I found a discussion about overriding the XalanDOM Tree structures at
http://marc.theaimsgroup.com/?l=xalan-dev&m=98403644905890&w=2, but my
question is how to effectively override the XalanDOM's String class, any
suggestion?? to do this, i think the data representation of the string
class must virtual.

mfg/regards
Tobias



Reply via email to