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

Richard Dobson richard at dobson-i.net
Mon Sep 30 10:39:05 UTC 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.

Richard




More information about the Standards mailing list