[standards-jig] NEW JEP: Inband Bytestream (JEP-0047)

chicago5 at gmx.de chicago5 at gmx.de
Mon Sep 30 05:44:08 CDT 2002


> ----- Original Message -----
> From: "Ben Schumacher" <ben at blahr.com>
> To: <standards-jig at jabber.org>
> Sent: Monday, September 30, 2002 11:08 AM
> Subject: Re: [standards-jig] NEW JEP: Inband Bytestream (JEP-0047)
> 
> > It seems me that it would be inefficient to use an encoding system that
> > already increases your CPU load (see the BommaNews site), and then have
> > to modify the output again to encode XML specials characters before you
> > send it over the stream. While it does decrease the network load, it
> does
> > increase the CPU load on both ends.
> >
> > By that reasoning, I guess its a trade-off on which is more important, a
> > lower bandwidth scheme, or a less computational intense scheme.
> 
> I would think that bandwidth use is the most important, and there also has
> to be the option of discovering if inband transport is allowed on the
> server, it has to be something a server admin can turn on and off, as it
> could potensially cost a lot in extra bandwidth.

I want to remind the discussion of the karma settings, which can be a very
annoying issue for transmitting data as "inband" data. 

-- 
Ulrich Staudinger http://www.die-horde.de http://www.igpp.de 
Product Manager @ http://complat.sourceforge.net/jnlp/ 
JID: uls at jabber.org 




More information about the Standards-JIG mailing list