Hello Darrell, Adam, >>>>> DRC wrote:
>> 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? You should extend existing encodings only in a way that would not break interoperability with existing clients and servers. E.g. you send some special pseudo-encoding code in SetEncodings, then the server may start using your particular extension to the Tight encoding. Note that such special pseudo-encoding code should be registered in the RealVNC's official RFB specification. As for extending the Tight encoding, I'd prefer that it would not be called "Tight" after any extensions or other changes have been introduced. That's just to prevent unnecessary confusion. -- With Best Wishes, Constantin _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
