Hi DRC, [snip] > > Unfortunately I don't think we can extend the Tight encoding. You > > should discuss this change with Constantin. > > > I'm not sure I understand how this works. Can someone enlighten me as > to how RFB extensions are registered and conflicts are avoided? If > there is no official registry for RFB extensions, then why am I > bothering to go through this process?
The VNC software and RFB protocol are maintained by RealVNC Ltd, including allocation of numbers for new encodings, etc. I've passed on your request for allocation of some encoding numbers for your project, and we'll get back to you shortly. > If we can't extend Tight encoding, then my counter-proposal would be to > create a new rfbEncodingTightNoZlib method. The Tight encoding was designed by Const Kaplinsky as part of the TightVNC project - I think Adam is simply suggesting that any proposed changes to that encoding need to be OK'd by Const, rather than break compatibility with his project. HTH, -- Wez @ RealVNC Ltd _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
