Unfortunately the parser masquerading as SAX in the .NET Framework
doesn't work like that. It will only raise the callbacks once it finds
the end of the document. For example, if you attach the parser to a
Jabber stream from a socket you will only get a callback for the
opening element, then the
JD and Kevin,
SAX parsers parse as the stream comes in. Your code gets callbacks on a
tag by tag basis. A DOM parser creates a complete document to
manipulate. If you're parsing is really simple, you can use a regular
expression to find what you're looking for.
Craig
On Fri, 2004-03-26 at 23:0
That sort of parsing is the basis of XMPP/Jabber. In many cases SAX and
DOM parsers do require the whole document. But there are parsers that
will parse a stream as it comes in. I'm not sure how it's usually done
in Java -- I'm a .NET guy myself -- but there are a few open source Java
Jabber lib
I am developing an IM client/server application for the visually impaired
that will make use of the Java Speach API. I am developing it as a senior
project and I am stuck on the XML parsing. I am having trouble finding a
technology that will allow me to parse XML incrementally. The client will
c
Tenny wrote:
I want to develop Jabber Source and Sink Application Can any body give me more idea about this
What you mean with jabber source and sink application? Can you give more
details?
___
jdev mailing list
[EMAIL PROTECTED]
https://jabberstudi
I want to develop Jabber Source and Sink Application Can any body give me more idea
about this
___
jdev mailing list
[EMAIL PROTECTED]
https://jabberstudio.org/mailman/listinfo/jdev
