RE: UltraVNC protocol extensions?

For feature requests and bug reports RC15 RC16. Please use the forum at http://forum.ultravnc.net/

Rudi,

Both the version 3.7 and 3.8 protocols allow custom protocol extensions to
be handled without losing compatibility with VNC, as I mentioned to you when
we were first developing them.

Regards,

Wez @ RealVNC Ltd.


> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf 
> Of De Vos Rudi
> Sent: 21 September 2005 19:49
> To: [email protected]
> Subject: Re: [Ultravnc-list] UltraVNC protocol extensions?
> 
> For feature requests and bug reports RC15 RC16. Please use 
> the forum at http://forum.ultravnc.net/
> 
> When we started ultravnc, there was no protocol extension 
> (like in 4.0) that could tell what kind of
> server you have.
> Lucky, all other versions had buildin that all versions 
> higher then 3.3 where mapped to 3.3
> This way we could differentiate between ours and the other 
> servers by handling the 3.6
> 
> I don't know if this is a "broken server", but as the 
> extension was added in rfb4.0 we where just to
> soon   :)
> 
> I just added some test exe that fix
> bug: using 256 colors and installed driver, colors where 
> sometimes inversted (red/blue)
> 
> Offical distribution are on sf, testversion can current be found on
> http://sc.uvnc.com/V2
> 
> 
> 
> Bob Friesenhahn schreef:
> 
> > For feature requests and bug reports RC15 RC16. Please use 
> the forum at http://forum.ultravnc.net/
> >
> > On Wed, 21 Sep 2005, James Weatherall wrote:
> >
> > > For feature requests and bug reports RC15 RC16. Please 
> use the forum at http://forum.ultravnc.net/
> >
> > Thanks.  Was not aware of the forum.
> >
> > > The only valid protocol versions are 3.3, 3.7, 3.8 and 4.0.
> > >
> > > The standard VNC viewer works around broken servers by 
> assuming that if they
> > > report a non-existent protocol version, then they can 
> probably support the
> > > next highest actual protocol version properly.  If a 
> server reports the
> > > non-existent version 3.6, therefore, VNC Viewer will ask 
> it to use protocol
> > > 3.3 in the hope that it can support that properly.
> >
> > So UltraVNC is considered to be a "broken" server? ;-)
> >
> > Thanks for the hint about versions.  I can at least get a session
> > established now.  My client was simply reflecting back the version
> > sent by the server and is supposed to be designed to handle multiple
> > protocols.
> >
> > Now there are just some wrong colors in the Hextile protocol to
> > contend with.  How odd!
> >
> > Bob
> > ======================================
> > Bob Friesenhahn
> > [email protected], 
> http://www.simplesystems.org/users/bfriesen/
> > GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by:
> > Tame your development challenges with Apache's Geronimo App 
> Server. Download
> > it for free - -and be entered to win a 42" plasma tv or 
> your very own
> > Sony(tm)PSP.  Click here to play: 
> http://sourceforge.net/geronimo.php
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App 
> Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> 



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php