When I upgraded to 2.0 (from 1.2a), I got a substantial performance boost, thanks to the replacement of the DOM implementation (with 1.7's IDOM). If you're already using IDOM, I doubt you'll see much, if any, gain. If my recent experience upgrading to 2.5 is any indication, you probably won't see any significant loss, either. I wondered if the pluggable memory manager would drag performance down, but in my tests, 2.5 performed slightly better than 2.0. (This seems miraculous to me. Kudos to the architects and authors of the code!)
You might want to consider your support needs as well. It's easier to get prompt, well-informed answers to questions about recent versions. This matters most if your app is undergoing active development, but could also make a difference if a question crops up at some future time. Also note that you may be able to reduce the amount of code you have to maintain by taking advantage of features implemented since 1.7. For instance, I finally ditched our serialization code because the DOMWriter has gotten good enough to meet our needs. (Well, with minor tweaks to suit my taste. I didn't like the blank lines it sometimes introduces between elements when pretty-printing.) -----Original Message----- From: Markus Harju [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 06, 2004 2:52 AM To: [EMAIL PROTECTED] Subject: v1.7.0 worth upgrading? Hi, I am using Xerces-C++ v1.7.0 to allow my Win32 application access data stored in two (big) XML files. Since it's so old now, I am wondering if it's worth the effort to try and upgrade it to past 2.0.0 ? I only need plain DOM handling with validated parsing. Are the newer releases heavier or "fatter"? Do they perform worse than 1.7.0 speed-wise? What else you gurus have to say about pros and cons? TIA, Markus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
