Hi Peter, No, there's no way to cope with incompatible viewers than to assume that they're just getting the protocol version wrong, or to disconnect them.
Regards, Wez @ RealVNC Ltd > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Peter Rosin > Sent: 15 May 2007 12:09 > To: [email protected] > Subject: Re: Bug in the RFB spec. > > On Tue, May 15, 2007 at 11:00:00AM +0100, James Weatherall wrote: > > Peter Rosin wrote: > > > Side note: a certain Windows only "VNC" client is a true > pest when you > > > are implementing a server and want to be compatible, that for sure > > > took some workarounds (Oh great, you can do 3.8, then I want 3.4, > > > oh and 3.4 means that I will do this and that and > whatnot. What crap). > > > The companion server in said "VNC" suite is more friendly. > > > How do other true VNC servers handle this rouge client? > > > > The only valid RFB protocol versions at present are 3.3, > 3.7, 3.8 and 4.0, > > so the "VNC viewer" that you're referring that reports RFB 3.4 isn't > > actually VNC-compatible. > > I know, but e.g. the RealVNC free edition server 4.1.2 doesn't bail > when a (broken) client requests 3.4, I was wondering if it > did anything > else to accomodate the (broken) client than treat it as if 3.3 had > been requested? > > Any pointers to where (when perhaps?) I can find the 4.0 spec? > > Cheers, > Peter > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
