[JDEV] SAX Parsing and server headers

[raditha dissanayake]

hang on a sec, the jabber server will not return the </stream:stream>
tag until you close the connection between the client and the server.

There are two ways in which you can overcome this.

The first approach would be to create an InputSource object from the 
InputStream of the client socket, most sax parsers can work with this 
safely.

The second on would be for you to treat each packet of data between the 
client and the server as separate xml documents and ask the parser to 
handle them individualy. However this approach would force you to 
process the
<stream:stream from='jabber.org' id='xxxx'
xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams'>

tag in some other way.










migs paraz wrote:

> Richard Dobson:
> 
>>Well for one the new server puts in <?xml 
>>version='1.0'?>, thats the main difference i can
>>
> see.
> 
> I was thinking about it and figured that this
> addition, or something else, breaks SAX. In my
> comparison between the output of a Java test program
> that echoes the socket input, and a tcpdump of the
> connection, I see that the Java program never sees the
> </stream:stream>.
> 
> Parser debugging time!
> 
> =====
> Miguel A.L. Paraz
> Metro Manila, Philippines
> Mobile: +639164237922
> 
> __________________________________________________
> Do You Yahoo!?
> Try FREE Yahoo! Mail - the world's greatest free email!
> http://mail.yahoo.com/
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 


-- 
Raditha Dissanayake
raditha at mediasolv.com
http://www.mediasolv.com/?rd