I use IDOM in a complex multithreading application.
Each thread gets an pointer to the same document and gets/sets different
attribute values many times during runtime. The IDOM is used - so to speak -
as common data structure for data exchange between the thread modules.

My experiences are:
IDOM is threadsafe! DOM not (really)!
IDOM is fast! (in my tests about 5-10x faster than DOM)
IDOM is more elegant for C++ programmer. (I love pointers!)

BUT!!

There is a problem with memory management. Once allocated memory is not
deallocated up to the deletion of the overall document. If you change the
value of an attribute many times the memory of the old value is not
deallocated for reuse and the document grows and grows. The only change
getting the memory back is the deletion of the overall document.

Markus


-----Urspr�ngliche Nachricht-----
Von: Richard Bolen [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 19. April 2002 16:24
An: Xerces C++ Dev List (E-mail)
Betreff: Difference between DOM and IDOM?


This is really more of a user question but...

What is the difference between the DOM and IDOM classes?  Are there
advantages/disadvantages to using one or the other?

Is there any documentation that explains the differences?

Thanks,
Rich

--------------------------------------------------------------------
Rich Bolen
Senior Software Developer
GretagMacbeth Advanced Technologies Center
79 T. W. Alexander Drive - Bldg. 4401 - Suite 250
PO Box 14026
Research Triangle Park, North Carolina 27709-4026  USA
Phone:  919-549-7575 x239,  Fax: 919-549-0421

http://www.gretagmacbeth.com/
--------------------------------------------------------------------


---------------------------------------------------------------------
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]

Reply via email to