Loading
SAX VS DOM

Java Quick Notes

Refresh Your Java - Before Java Interview

We are Agile, believe in less Documentation - Only Quick notes (Java Interview Questions) of Java/J2ee Read more....


Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet

Go to SiteMap

Q)  SAX VS DOM ?


Ans)

The SAX parser doesn't create any internal representation of the document, so it can scan
and parse gigabytes worth of XML documents without hitting resource limits because it does
not try to create the DOM representation in memory. Instead, it raises events that you can
handle as you see fit. Because of this design, the SAX implementation is generally faster
and requires fewer resources.

On the other hand, SAX code is frequently complex, and the lack of a document representation
leaves you with the challenge of manipulating, serializing, and traversing the XML document.

With SAX parser you could not traverse back once an elemented is processed, but with DOM
you can traverse through back and froth.



Back to top

------------------------- We hope you got necessary Info On -----------------------------------------

SAX VS DOM


SAX VS DOM

-------------------------------------------------------------------------------------------------------



Face Book
Request for a Mock Interview/Training

Get a PDF

Face Book
Same look (Read) on any device, this is Ads free