RE: RE: Compatibility issue with MacOS X VNC clients? (was: Slightly OT - Best MAC OS X VNC?)
"James Weatherall" <[email protected]>
| Newsgroups | gmane.network.vnc.ultravnc.general |
|---|---|
| Organization | RealVNC Ltd. |
| Message-ID | <000201c53627$55f744e0$0300a8c0@solid> |
For feature requests and bug reports RC15 RC16. Please use the forum at http://forum.ultravnc.net/ Rudi, The document you refer to describes RFB 3.3. We have since defined RFB versions 3.7 and 3.8 (see http://www.realvnc.com/docs/rfbproto.pdf for the current version). There is no such thing as the "RealVNC rfb protocol", just things that are VNC-compatible and things that aren't. UltraVNC is not VNC-compatible because no effort has been made to ensure compatibility with versions of the RFB protocol other than 3.3. Without looking into things in more detail I can't say for sure, but I suspect that UltraVNC also uses non-existent encoding numbers for some of its protocol messages, so it's not even RFB 3.3. compliant. I sent you some details about how to use custom protocols while retaining compatibility with the RFB protocol and standard VNC software some time ago - would you like me to send you those details again? Cheers, Wez @ RealVNC Ltd. -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: 31 March 2005 19:14 To: [email protected]; [email protected] Subject: RE: RE: [Ultravnc-list] Compatibility issue with MacOS X VNC clients? (was: Slightly OT - Best MAC OS X VNC?) We perfect follow the rfb protocol has it was orignal published in 1998 by Tristan Richardson and Kenneth R. Wood. (§5.1.1) Protocol version consist of 12 bytes. (001.001, 003.099, 004.012) "Handshaking begins by the server sending the client a ProtocolVersion message. This lets the client know which is the latest RFB protocol version number supported by the server. The client then replies with a similar message giving the version number of the protocol which should actually be used (which may be different to that quoted by the server)." UltraVnc follow the 1998 rfb protocol and not the newer "RealVNC rfb protocol" It is compatible with all VNC viewers/servers that follow the 1998 rfb protocol, if not, there have to be a bug in the code :) Rudi For feature requests and bug reports RC15 RC16. Please use the forum at http://forum.ultravnc.net/Sam,It also seems that tha UltraVNC viewer component also reports a non-existentversion number, but a different one from the UltraVNC server! :)Cheers,Wez @ RealVNC Ltd.-------------------------------------------------------This SF.net email is sponsored by Demarc:A global provider of Threat Management Solutions.Download our HomeAdmin security software for free today!http://www.demarc.com/info/Sentarus/hamr30 ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30