[jdev] VTD-XML version 1.6

[crackeur at comcast.net]

if by streaming you are referring to SAX parsing, I am reasonably comfortable,
SAX will be obselete because of a multitude of issues...

I wrote an article on java world entitle simplify XML processing with VTD-XML

-------------- Original message -------------- 
From: Ralph Meijer <jabber.org at ralphm.ik.nu> 

> On Thu, May 18, 2006 at 09:56:04AM +0200, Michal vorner Vaner wrote: 
> > On Thu, May 18, 2006 at 09:18:52AM +0200, Ralph Meijer wrote: 
> > > On Thu, May 18, 2006 at 12:10:41AM -0700, Jimmy Zhang wrote: 
> > > > The other issue, the way I understand Jabberd, it is a router, how can 
> > > > one not waiting for the entire document to arrive before routing the 
> > > > message? 
> > > > Also what kind of performance jabberd is performing? Do it have to 
> > > > occasionally modify XML data? 
> > > 
> > > Jabber works using direct childs of the root element as the unit of 
> > > communication, not the whole document. Entities basically open a TCP 
> > > connection and then during the whole session (which may last days or 
> > > even longer) two XML documents are being exchanged. One in each 
> > > direction. 
> > > 
> > As I have seen, most jabber libraries have SAX parser to split it into 
> > the stanzas (these child elements) and there is something like semi-dom 
> > something to take care of each one. And I guess there will not be much 
> > difference in the parsers, if it is already split up and built to some 
> > kind of tree, or joined to gether and passed to any special parser to 
> > parse it again. And anyway, these pars are rather small - usually few 
> > bytes. 
> 
> Sure. Jimmy didn't seem to understand how XML Streams work, so I gave a 
> small overview. The point is that he send a message that appears to be 
> targetted at the larger XML community and someone asking if this stuff 
> actually works for Jabber. It looked like spam to me initially, too. 
> 
> -- 
> Groetjes, 
> 
> ralphm 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20060519/119853c5/attachment-0002.htm>