yes he's right, SAX is faster because SAX doesn't let you modify the document, you can only parse the document to read it.
----- Original Message ----- From: "Bhushan_Bhangale" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 15, 2002 9:49 AM Subject: Re: Performance of Xerces & Xalan No you are wrong infact SAX in faster as it doesn't read the whole document and keeps into memory. -----Original Message----- From: Suresh Addagalla [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 12:46 PM To: [EMAIL PROTECTED] Subject: Performance of Xerces & Xalan Excuse me for asking an off-topic question, but thought that many servlet developers would be familiar with this. In my servlet application, I need to transform XML data and send HTML response. For XML parsing and transforming, I came across Xerces and Xalan from Apache. But I would like to know if some one has worked on the same and has an idea about them from the performance point of view with respect to other XML parsers/processors available for Java. Since these tools have both DOM and SAX implementations, I guess DOM is faster if memory requirements are met? I need my application to be fast and also scalable. Any better alternatives, ideas?? Thanks, Suresh ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
