Skip to main content

DOM Parser Vs. SAX Parser


Many developers sometimes confuse which is better to parse the XML document. Ofcourse myself also got doubt which parser I can use for this situation.  Since I have read about DOM and SAX very long back. Just refreshing it again

DOM (Document Object Model) Parser:
  • Tree model parser(Object based) (Tree of nodes).
  • DOM loads the file into the memory and then parse the file.
  • Has memory constraints since it loads the whole XML file before parsing.
  • DOM is read and write (can insert or delete the node).
  • If the XML content is small then prefer DOM parser.
  • Backward and forward search is possible for searching the tags and evaluation of the information inside the tags. So this gives the ease of navigation.
  • Slower at run time.
SAX (Simple API for XML Parsing) Parser: 
  • Event based parser (Sequence of events). Event based means..don't be confused with word "event". Here event means. (e.g. <something>), then it triggers the tagStarted event (actual name of event might differ). Similarly when the end of the tag is met while parsing (</something>), it triggers tagEnded. Using a SAX parser implies you need to handle these events and make sense of the data returned with each event.
  • SAX parses the file at it reads i.e. Parses node by node.
  • No memory constraints as it does not store the XML content in the memory.
  • SAX is read only i.e. can’t insert or delete the node.
  • Use SAX parser when memory content is large.
  • SAX reads the XML file from top to bottom and backward navigation is not possible.
  • Faster at run time.
Conclusion : DOM Parser is better over SAX Parser, if the XML document is small. If you don't know the size of  a XML, I mean size is huge go for SAX Parser. 

Comments

Popular posts from this blog

Asynchronous Vs. Synchronous Communications

Synchronous (One thread):   1 thread -> |<---A---->||<----B---------->||<------C----->| Synchronous (multi-threaded):   thread A -> |<---A---->| \ thread B ------------> ->|<----B---------->| \ thread C ----------------------------------> ->|<------C----->|

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag

Advantages & Disadvantages of Synchronous / Asynchronous Communications?

  Asynchronous Communication Advantages: Requests need not be targeted to specific server. Service need not be available when request is made. No blocking, so resources could be freed.  Could use connectionless protocol Disadvantages: Response times are unpredictable. Error handling usually more complex.  Usually requires connection-oriented protocol.  Harder to design apps Synchronous Communication Advantages: Easy to program Outcome is known immediately  Error recovery easier (usually)  Better real-time response (usually) Disadvantages: Service must be up and ready. Requestor blocks, held resources are “tied up”.  Usually requires connection-oriented protocol