Wed Nov 19 14:42:00 2003
I setup vnc to reject non-shared connects, when there is already a
session, because the users of this system dont want to throw each other
out. now if someone tries to connect, the message "server quit
unexpectedly" is displayed in that case.
for the sake of us humans, could you anticipate this in the protocol and
in the release verison instead display a message like "the server is in
use already." and if the server doesnt force non-shared connects,
probably suggest "you may want to make a 'shared connection'" with a
button to do so or cancel?
this is with the beta4 server, which is production quality, I'd say, and
I cant help being cynical, on a fully patched w2k box, which does not meet
this standard, despite the fact that "someones rear end is @stake" (:
thank you for this solid piece of open source software.