>you can call these "network issues" but it is tcp after all and packets do
>get lost.
Ummm... UDP is the unreliable protocol family. TCP has guaranteed in-order delivery
of all packets. If that guarantee is broken, the connection is supposed to be
severed. If you are actually losing TCP packets without losing the connection, one or
both TCP/IP stacks would seem to be broken... If a networking guru knows otherwise,
it would be useful information.
I have however noticed a behavior that makes it very difficult to debug vncviewer. I
have been working on CE viewer, which requires compiling on a Windows machine. That
being the only machine readily available to run the server on, I have the viewer under
debug connect to the development Windows machine. There are certain points during the
connection process (I believe it is during the initial screen download, but I'm not
certain -- not debugging the server) that if I terminate the viewer, the server locks
up my development machine. Mouse moves, but can't click on anything or type anywhere.
I have to three-finger and terminate WinVNC, and then I can get control of the
machine back. So it would seem that there are places in WinVNC that do not gracefully
handle severing of the connection.
Mac
_____________________________ /"\
Mac Reiter \ / ASCII Ribbon Campaign
Nomadics, Inc. X Against HTML Mail
[EMAIL PROTECTED] / \ (To join the campaign, simply use
this in your signature.)
---------------------------------------------------------------------
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
---------------------------------------------------------------------
