Wez:
I think I understand. Is there any in-situ test (e.g., an
operation of any sort that's unsupported) I could run which would
demonstrate the incompatibility? Or...is it incompatible in the
similar sense that some native French speakers don't believe that
native Quebecers speak French? :)
thanks,
Scott
On Wed, 3 Jan 2007, James Weatherall wrote:
Hi Scott,
Sorry, perhaps I wasn't clear - UltraVNC isn't VNC compatible to the best of
my knowledge, because it uses a custom protocol on-the-wire that, although
based on the old RFB 3.3 protocol, isn't compatible with it. If you've
based your project on that codebase then, unless you've taken out the
incompatible bits, your project won't be VNC compatible either.
Cheers,
Wez @ RealVNC Ltd.
-----Original Message-----
From: Scott C. Best [mailto:[EMAIL PROTECTED]
Sent: 03 January 2007 17:23
To: James Weatherall
Cc: [email protected]
Subject: RE: speaking of firewalls...EchoVNC 2.0 is now available
Wez:
Hello, and Happy New Year! Thanks for writing. I
probably misused
the term "VNC-compatible" -- I meant it to indicate that the EchoVNC
server accepts both direct and echoWare-relayed connections from the
RealVNC Viewer, and the RealVNC server accepts both direct
and relayed
connections from the EchoVNC Viewer. If there's something
else I should
add (remove?) to our flavor to maintain VNC compatibility,
please point
me to the details and I'll pursue it.
Regarding the Mirror-Driver problem, you are right, and we're
working on a Mirage-Driver update for the next release.
cheers,
Scott
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
