[Standards-JIG] JEP-0017 Framing: Why was it rejected?

Heiner Wolf wolf at bluehands.de
Wed Oct 20 17:47:48 UTC 2004


Hi,

> To Bob: the main argument against framing is probably just 
> that it makes the protocol less clean-looking.  The notion of a streamed XML 
> document that you can throw right at a SAX parser is compelling.  Sure, it is 
> possible to implement specs like JEP-0017 that graft on framing, but how 
> much sense does it make to skip over a piece of what is supposed to be a 
> continuous document?

It makes sense in some applications. When the XMPP RFC news hit slashdot.org the only concern was that XMPP is not suited for large scale applications. Message routers must parse all traffic just to find destination addresses. Some people say that in order to process 10.000.000 messages per minute (even distributed over many processors) you need to get to the destination address quickly. You need framing, because 10.000.000 XML parsers cost way too much CPU. Maybe time and performace increases invalidate this argument. But it would be interesting to know what really is the bottleneck in todays very large messaging networks. 

http://developers.slashdot.org/article.pl?sid=04/10/05/0226233&tid=215&tid=95&tid=185&tid=8

hw
--
Dr. Klaus H. Wolf
bluehands GmbH & Co.mmunication KG
http://www.bluehands.de/people/hw
+49 (0721) 16108 75
--
Jabber enabled Virtual Presence on the Web: http://www.lluna.de/
Open Source Future History: http://www.galactic-developments.com/



More information about the Standards mailing list