Hi Jason, I have implemented everything except for fixing the IDOM memory model to not grow uncontrollably. My only performance test to this point has been to compare IDOMCount and DOMCount and found that they take the same amount of time. You had earlier pointed me to the xmlbench tests that AndyH, but found that the memory leak prevented them from completing. So I (or someone) needs to fix the memory problem first. I plan at taking a look at the memory problem later this week, so I can let you know more after that.
Performance is very important, thus why I support using the IDOM as the implementation. Though, I don't think that IDOM represents the best external interface from a design and usability standpoint. I believe that the developers of IDOM gained their performance boost by providing each document its own memory manager, not by eliminating reference counting by itself, and that the DOM style interface is both easier to use and provides needed isolation between users and the DOM implementation. Lenny -----Original Message----- From: Jason E. Stewart [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 3:33 PM To: [EMAIL PROTECTED] Subject: Re: DOM 3 Patches? "Lenny Hoffman" <[EMAIL PROTECTED]> writes: > I have been working on a write up that describes my view of the > Xerces DOM, it is not complete yet, but since I haven't heard from > you on your position, I have included it below so that you and > anyone else interested can comment. Lenny, Have you been able to implement this and run the appropriate timing tests? jas. --------------------------------------------------------------------- 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]
