Yes, every apps pretty much do that using DOM and SAX?
but DOM is the in-memory representation, not what gets sent on
the wire? When you route, you have wait for the message to arrive..
because in general the app logic depends on data that could reside
any where in the XML message....
What do jabber put on the wire? It got to be XML right?
-------------- Original message --------------
From: Michal vorner Vaner <[EMAIL PROTECTED]>
--- Begin Message ---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.-- Work with computer has 2 phases. First, computer waits for the user to tell it what to do, then the user waits for the computer to do it. Therefore, computer work consists mostly of waiting. Michal "vorner" Vaner
pgpKuxi17sHUl.pgp
Description: PGP signature
--- End Message ---
