On Thu, Jul 08, 2010 at 01:20:31PM +0200, Pierre Ossman wrote: > On Thu, 8 Jul 2010 10:45:13 +0100 > "Daniel P. Berrange" <d...@berrange.com> wrote: > > > Of interest to folks on this list.. I've just noticed work on qemu-devel > > proposing a new variant of the Tight framebuffer encoding that uses PNG > > for compression instead of JPEG: > > > > http://lists.gnu.org/archive/html/qemu-devel/2010-07/msg00445.html > > > > "Tight PNG > > ========== > > This set introduce a new encoding: VNC_ENCODING_TIGHT_PNG [1] (-260) > > and a new tight filter VNC_TIGHT_PNG (0x0A). When the client tells > > it supports the -260 encoding, the server will use tight, but will > > always send encoding pixels using PNG instead of zlib. If the client > > also told it support JPEG, then the server can send JPEG, because > > PNG will only be used in the cases zlib was used in normal tight. > > > > This encoding was introduced to speed up HTML5 based VNC clients like > > noVNC but can also be used on devices like iPhone where PNG can be > > rendered in hardware." > > > > > > I know the encoding -260 has already been allocated for use by QEMU, > > but I'm not sure who is maintaining the authority for tight filter > > numbers & can thus records/approves the use of 0x0a ? Is the latter > > something we should be doing here if no one else is an authority > > for tight filters ? > > > > I'd say it's the TightVNC people who are the authority to any changes > to the Tight encoding. I'm not sure any of them are subscribed to this > list though. > > I'm wondering why the integration into an existing encoding though? > This extra layer of tight encodings on top of the normal encodings is > just extra overhead and is not something that we should be promoting > going forward.
+1 I also think it would be better (and easier for implementation) to mark PNG as "full-fledged" encoding. Then we can easily sync it with RealVNC's RFB specification. Regards, Adam -- Adam Tkac, Red Hat, Inc. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ tigervnc-rfbproto mailing list tigervnc-rfbproto@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-rfbproto
