Listener that spawns processes instead of threads

[howardcshaw]

When using SingleClick to support multiple people, I have been frustrated by one slow connection making them all unusable, one connection dying taking them all down, and one connection dropping with the chat open making all the sessions refuse to close because the chat is open and can't be closed. Also, I have noticed a general system instability that increases over time, and seems to be tied to the number of reverse connections I have had.

I played with the source for 1.0.5 today, and I was fairly easily able to get the vncviewer to spawn a new process instead of a thread, which handily solves most of these issues, by isolating each SingleClick connection.

My tweaks are not internationalized nor set up on options and such, but I would be happy to explain the few changes I made.

I think having a command-line option to switch between multiple threads per reverse connection, and multiple processes, would make supporting multiple customers much easier.

P.S. It was really great downloading the source to 1.0.5 and discovering that it builds happily in Visual Studio 2005... though I did have to go back to an older tarball to get the Tango bitmaps from the vncviewer res directory to get my icons.

[gimel]

one connection dying taking them all down, and one connection dropping with the chat open making all the sessions refuse to close because the chat is open and can't be closed

I agree 100%. This is a total pain to have these problems whereas we are in a multi-process environment.