<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML><HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<STYLE></STYLE>
<META content='"MSHTML 5.00.0910.1309"' name=GENERATOR></HEAD>
<BODY bgColor=#ffffff>
<DIV>
<DIV>
<DIV>Sorry for the length.</DIV></DIV>
<DIV>Hello,</DIV>
<DIV> </DIV>
<DIV>
<DIV>I am developing a client side application which expects a DOM object tree
</DIV></DIV>
<DIV>of an XML stream coming from the server as a result of an HTTP
request.</DIV>
<DIV>To provide the app. with the DOM tree, a DOM XML parser will sit </DIV>
<DIV>in between the XML stream and my app.</DIV>
<DIV>The parser will convert the XML stream to a DOM object tree</DIV>
<DIV>and pass it on to my application.</DIV>
<DIV>I am confused about where to place the DOM XML parser</DIV>
<DIV>I have thought of 2 places where the parser could reside </DIV>
<DIV>but am not sure which place in better.</DIV>
<DIV>I'd be grateful if someone could help.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>XML DOM PARSER POSITIONS I THOUGHT OF </DIV>
<DIV> </DIV>
<DIV>1) Any browser which supports XML should have an inbuilt XML parser.</DIV>
<DIV>Assuming the parser is a DOM complaint one I could use the browser </DIV>
<DIV>inbuilt parser to get the DOM tree of a served XML stream.</DIV>
<DIV>This would mean </DIV>
<DIV>- that an XML stream would first go to a browser </DIV>
<DIV>- then I would have to trap the browser processing when a DOM tree is
formed</DIV>
<DIV>- Retrieve the DOM tree</DIV>
<DIV>- Pass it on to my app.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>2) Use a stand alone DOM XML parser which I could incorporate into</DIV>
<DIV>my app.This would mean</DIV>
<DIV>- that an XML stream would come straight to the XML parser in my app.</DIV>
<DIV>bypassing the browser totally</DIV>
<DIV>- the XML parser would produce the DOM tree</DIV>
<DIV>- The DOM tree would then be passed to the app. </DIV>
<DIV> </DIV>
<DIV>QUESTIONS</DIV>
<DIV> </DIV>
<DIV>1) Which of the 2 approaches should I use for the DOM tree generation</DIV>
<DIV>and why?</DIV>
<DIV>2) Any existing samples/applications which expect DOM trees
</DIV>
<DIV>as input for processing XML data </DIV>
<DIV>and how they manage to get the DOM trees? </DIV>
<DIV> </DIV>
<DIV>Thanks in advance for any replies,</DIV>
<DIV> </DIV>
<DIV>
AMIT</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV></DIV></BODY></HTML>