stream compression (was: Re: [jdev] Re: Jive Messenger is now Wildfire Server)

Justin Karneges justin-keyword-jabber.093179 at
Sun Dec 18 20:33:36 CST 2005

On Sunday 18 December 2005 14:06, Remko Troncon wrote:
> > i dont think there are clients which suport it yet. Its a big loop.
> > Client developers are waiting for servers and vice versa.
> > I have also prepared code and no chance to test it yet because of
> > missing servers.
> Are there any estimations on how much a normal sream consumes in bandwidth,
> compared with a TLS stream, a TLS compressed stream, and a ZLib compressed
> stream ?

I believe TLS compression is commonly done with Zlib.  Thus, if you are using 
TLS, you could use either TLS compression or the compression JEP to achieve 
the same thing.  The nice thing about TLS compression is that it is 
transparent, and probably very easy to enable in any software using OpenSSL, 
if any enabling has to be done at all.

The stream compression JEP seems useful in 3 situations:
  1) You aren't encrypting at all
  2) You're encrypting only with SASL
  3) The TLS implementation can't do compression

#1 is a terrible reason to use the JEP, but the others are quite reasonable.

That said, most Jabber software uses OpenSSL and doesn't use SASL encryption.  
Therefore, this might be a reason why the JEP hasn't gained much attention.


More information about the JDev mailing list