[Standards] XEP-0138 vs. TLS compression

Jonathan Chayce Dickinson chayce.za at gmail.com
Thu Aug 30 20:29:13 UTC 2007

"EXI compression *combines* knowledge of XML with a *widely adopted, 
standard compression algorithm* to achieve higher compression ratios 
than would be achievable by applying compression to the entire stream."

"which are individually well suited for standard compression algorithms"

If EXI compression is set to true, you SHOULD send the document through 
a compression library.

Boyd Fletcher wrote:
> nope. would result in larger message sizes in most cases
> On 8/30/07 2:56 PM, "Justin Karneges"
> <justin-keyword-jabber.093179 at affinix.com> wrote:
>> On Thursday 30 August 2007 10:50 am, Peter Saint-Andre wrote:
>>>> As far as I understand it, Efficient XML is more than just a compression
>>>> algorithm. In order to prevent developer confusion, I think it might be
>>>> helpful to write a XEP that describes how Efficient XML is to be used in
>>>> the context of XMPP applications. That XEP could also register an item
>>>> to be added to the compression algorithms registry.
>> And this may be a dumb question, having not read the Efficient XML spec, but:
>> would it be desirable to compress (e.g. with ZLIB) Efficient XML?
>> -Justin

jonathan chayce dickinson
ruby/c# developer

cell:   +27741863698
email:  chayce.za at gmail.com
jabber: moitoi at inflecto.org

<some profound piece of wisdom>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6974 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070830/5600359f/attachment.bin>

More information about the Standards mailing list