[Standards] Stream Compression: When to advertise and allow compression? XEP unclear and clonflicting with itself.

Tobias Markmann tmarkmann at googlemail.com
Tue Aug 18 19:43:46 UTC 2009


On Tue, Aug 18, 2009 at 9:09 PM, Fabio Forno <fabio.forno at gmail.com> wrote:

> Compressing an encrypted stream is simply pointless: encryption
> maximizes entropy, so you can't have any gain but consuming resources.
>

I understand that but why enforcing it so much in the order, I mean tkabber
for instance only works when compression is advertised before SASL with
works nicely with ejabberd. Both projects supported compression before
XEP-170 described how it should work.

Tobias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20090818/e94d7690/attachment.html>


More information about the Standards mailing list