[jdev] [ANN] Jive Messenger is now Wildfire Server

[Matt Tucker]

Tjil,

Thanks for the link. I filed the following issue:

http://www.jivesoftware.org/issues/browse/JM-493

It sounds like using Jzlib is the right approach. The main problem we
ran into when committing stream compression support was a lack of other
implementations to test against for compatibility. Does anybody know of
clients that support the JEP that we could test with?

Thanks,
Matt   

> -----Original Message-----
> From: jdev-bounces at jabber.org 
> [mailto:jdev-bounces at jabber.org] On Behalf Of Tijl Houtbeckers
> Sent: Sunday, December 18, 2005 11:59 AM
> To: Jabber software development list
> Subject: Re: [jdev] [ANN] Jive Messenger is now Wildfire Server
> 
> On Sun, 18 Dec 2005 20:07:54 +0100, Jakob Schroeter 
> <js at camaya.net> wrote:
> 
> > Indeed, debug.log contains the following:
> >
> >  ...
> >  java.util.zip.ZipException: no current ZIP entry  at 
> > java.util.zip.ZipOutputStream.write(Unknown Source) ...
> 
> Now, I haven't been looking at the Wildfire source or 
> anything, but it's highly unlikely you can write a zlib 
> compatible (as specified in the stream compression JEP) 
> output with a ZipOutputStream, since that writes output 
> specific to the ZIP file format. For "pure" ZLIB you can use 
> DeflaterOutputStream and InflaterInputStream. 
> (ZipOutputStream and ZipInputStream actually extend these). 
> However AFAIK these still do not give you the ability to do 
> "partial flushes" on your output which is needed to get good 
> compression for XMPP.
> 
> Thankfully, there is a lib available to do this:  
> http://www.jcraft.com/jzlib/index.html (also explains the 
> problem with the Sun implementation a bit more). It's also 
> pure Java so you won't be vonurable to any ZLIB exploits.
>