Yes - the protocol document is designed to fully and comprehensively document all currently used popular extensions (Palm scaling, tight enconding, gzip stuff, etc) and try to make a simpler protocol that all servers and clients can use. As I own platforms that are 32 bit LE, 64 bit LE, and embedded 32 bit BE, and soon will own an iLamp (32 bit BE), with four different operating systems, you can be assured that I do think very seriously about compatibility and cross-platform issues.
If everyone looks at the draft, it's made up to be submitted to the IETF for consideration as a draft. I still think that this would be a good idea as it will help us make RFB the default remote control protocol for products. And the IETF generally don't accept protocols/standards that lock people into one platform. Andrew ----- Original Message ----- From: "Alex Angelopoulos" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 15, 2002 4:04 AM Subject: Re: RFB Protocol > The SecureVNC notes at SourceForge mention targeting both Win32 and POSIX systems.. > > In any case, the protocol issues are platform-independent - or should be ;). --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------