> Jay, could you maybe explain how the current process works? Currently this > is what I imagine the process to work(from what I have read from your > documentation) > > A xrdp client connects to the xrdp server, and preliminary authentication > details and encryption semantics are exchanged. Then, the xrdp server > connects to sesman, who authenticates the user, and selects an existing > session or creates a new Xvnc session. Then the connection from xrdp to > sesman is dropped.
exactly. > So to implement these capabilities, xrdp would have to stay connected to > sesman the whole time the user is connected. So when xrdp sees that a user > disconnects, it should relay that information to sesman, who then kills the > Xvnc session? Yes, but sesman should only kill the session if setup to do so(KillDisconnected). I can even explain which .c files need to be edited. There is a new version of the xrdp - sesman protocol that Simon and I started but never quite got finished. I think this was one of the new features. Jay ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
