>From what I understand, ECS works exactly the same way DOM does. That is, it keeps the entire document structure in memory and spits it out at the end. The alternative to DOM is SAX, though I have never used SAX to write a document, so I am unsure whether it is possible to write or not (though I would think it is). SAX documents are not held in memory, rather it spits out events (when read) as the parser moves through the document. SAX is generally recommended for use when parsing (or writing?) large XML documents.
Matt. -----Original Message----- From: Jim Palm To: [EMAIL PROTECTED] Sent: 20/12/02 1:39 PM Subject: Does ECS use less memory than DOM? Hi - We need to continuously generate several large XML documents for our application. We were considering using DOM (or dom4j, etc) to first create a DOM document in the memory and then serialize it to a file. But we are concerned about memory and performace issues related to DOM. So we are considering ECS. Is it really a better idea to use ECS instead of DOM to greate XML documents (from memory/performance point of view)? From what I understand, ECS is just a cool way of using StringBuffer.append() operations. Am I correct? Also, any idea on when ECS 2.00 will be out? Many thanks. (and have a nice Xmas too!) PS: Also, a little more documentation might be helpful. Jim Thanks __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
