On Mon, 21 Nov 2011 16:20:52 -0600 Matt B <empe...@mightypenguin.org> wrote:
> Hi all, > > Working on getting zlib and related protocols working on noVNC and have hit > an issue. The first zlib packet seems to inflate and draw correctly, but > the second or third zlib packet I get is a 32 or 64 byte piece of > compressed data that I'm not sure what to do with. It inflates to around > 610ish bytes. > > Any ideas? > I haven't looked at the code, but have you made sure you keep the zlib state between packets? The zlib stream is generally never restarted during the lifetime of a connection, so you need to keep it around for multiple updates. Rgds -- Pierre Ossman OpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio AB Web: http://www.cendio.com A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
