Hi Ran, I don't think anyone would dispute the hard work that's gone in to either of TightVNC or UltraVNC!
The issue in this instance is simply that the UltraVNC software, while based on our VNC 3 series codebase, breaks the protocol versioning scheme of the RFB protocol and so is not VNC-compatible. The TightVNC project adheres to the protocol, to the best of my knowledge, and so retains compatibility. I hope that clarifies things for you, but feel free to contact me off-list if you have further questions. Cheers, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Ran Sasson @ I.O. Ltd. > Sent: 02 February 2007 23:41 > To: Kelly F. Hickel > Cc: Steve Bostedor; James Weatherall; [email protected] > Subject: Re: Maybe Spam: RE: Hitachi-ZYWRLE Encoding Number > (was RE: Introduction of New VNC codec) > > > On 2/3/07, Kelly F. Hickel <[EMAIL PROTECTED]> wrote: > > > I might be wrong, but that's the way I read it.... > > > I think the issue is bigger than that. You see, James > addresses these as "side"/"minor"/"hobby" projects, while as said: > They ARE 100% compatible with the original VNC code base and > largely used. [snip] _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
