which version of Xerces are you using? Last summer I have changed the storage model for the setUserData/getUserData to use less memory and to be faster; if you are not using Xerces 2.6, could you try it and check if it is acceptable?
As for attaching the user data to every node, I guess that would be unacceptable to the users of Xerces that don't use user data (and I think they are the vast majority); 32 bit of unused payload on each node would quickly add to a considerable amount of memory.
Alberto
At 16.03 15/01/2005 +0100, Fulvio Risso wrote:
Dear all,
I'm experimenting the same problem reported by [EMAIL PROTECTED] in June 2003 (http://www.mail-archive.com/xerces-c-dev@xml.apache.org/msg09638.html)
I have a big XML tree and I use DOMNode::setUserData() / DOMNode::getUserData() to associate some custom data to most of my DOM elements. However, these functions are very slow because they use a global hash list and they became the bottleneck in my application.
However, from an architecture point of view, I believe data should be attached to every single node instead of using a global list.
Does anyone has any suggestion in order to avoid such this problem? Is there any plan to modify the implementation of these functions?
Thank you very much,
fulvio
(another open source software developer) analyzer.polito.it windump.polito.it winpcap.polito.it www.nbee.org
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
