Where can I get the docs for RFB 4.0/5.0 ? And
Can we add a request in the RFB protocol to query for the pointer/keyboard
state ? ie x,y coordinate of the pointer and the state of capslock etc key.
-shashi
-----Original Message-----
From: Stig A. Olsen [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 16, 2001 3:51 AM
To: [EMAIL PROTECTED]
Subject: RE: RFB Protocol 4.0 - encodings wanted
Just a side note here: My company has just released a new software version
for our videoconferencing equipment that support a VNC client (RFB 3.3).
Since VNC is GPL we naturally had to handcode everything from scratch based
on the RFB documentation (we can't release the source since we're using a
single linked image that contains source code from other vendors, such as
the embedded operating system - and we surely don't want to violate the
GPL).
I think that getting more and more support for VNC is a "good thing", so I
just hope that further RFB releases do not make too extensive use of other
full GPL'ed packages that will be "close to impossible" to recode for more
specialized targets. If one could try to use a bit more liberal licenses
(such as LGPL or even BSD) I think that would help a lot. We're absolutely
not trying to capitalize on GPL based software, we just thought that VNC was
the best thing out there to get this kind of support for our systems (also
since we're then not strictly tied to the Windows platform when it comes to
the server side).
best regards,
Stig A. Olsen
www.tandberg.net
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tristan
> Richardson
> Sent: Monday, July 16, 2001 11:58 AM
> To: Andrew van der Stock; [EMAIL PROTECTED]
> Subject: Re: RFB Protocol 4.0 - encodings wanted
>
>
> We already use RFB version 4.x in some of our projects.
> We're now developing
> version 5.0 of the protocol which is a substantial change
> from the version 3
> protocols. It would be good to coordinate over what version
> number you choose
> for your new protocol so that we don't release incompatible
> protocols which
> claim to be the same version number. That would be bad :-)
>
> Cheers
>
> Tristan
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
