Roland wrote: > Hello, I have spent some thoughts of session management in vnc (also > loadbalancing) > and would like to present a little conecpt, which would need just little > change to > existing vnc (and no change to protocol at all) > > [1] = vncviewer Wrapper (reference implementation perl, later C, included > inside > vncviewer) > [2] = Xvnc Dispatcher/Wrapper (perl)
[...] Whoa, load balancing too! You've got big plans. I can't say if this is a good way to balance load or if it should be handled on some other level, but I agree that if it's done on the VNC level, then it propably shouldn't be integrated in the VNC server but handled by a separate program. This looks like it should work. I see one problem though: If two VNC servers are started at the same time they may try to use the same display number. You need a way to verify that a newly started XVNC actually got the display number you told it to use. All kinds of wrappers that start XVNC have this problem, but the more users you have, the higher the risk gets. > - Existing vncviewer does not take password via commandline (could be fixed > easily) There needs to be another way to communicate the password, at least in Unix-like systems with more than one user, since any user can see the full command line of any running process. > - how to differ between "disconnect" and "terminate" a vnc session ? You could do it like in normal X sessions where there is a process that acts as "the session". When this process terminates, the X server is killed (if it was started by Xinit) or reset (if it's managed by XDM). Bjvrn Persson _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
