Follow up from #41.
It would be nice if the clients could specify more than sharing on or off. Maybe add the ability to refuse to let other users steal the session? ("keep"?) The other user would have to issue an "xpra disconnect" first before being able to connect? We still need a way to take over stuck sessions, otherwise the only option would be to "xpra stop" it which isn't very user friendly.
See also #1369: the sharing option could be used to define the offset for each client. Taking this even further: we could even have the option to force the client to map to the same full-screen size (scaling client size display to match whatever is on the server) - somewhat related to #972.
too late to make changes, re-scheduling
Sharing code has been refactored into a utility method handle_sharing() in r16712 so RFB (#1620) can make use of it.
Done in r17268 with the "lock" option, which can be modified at runtime from the system tray.
The semantics of "sharing" has changed somewhat, this is how the server handles the value:
"auto" defaults to "no" on the client.
The same logic applies to the new "lock" switch. A locked session cannot be stolen by another user, though it may still be shared if that is enabled.
@maxmylyn: mostly a FYI. Feel free to close. I may follow up in #1369 and #972.
r17274 allows the "lock" and "sharing" attributes to be changed at runtime, either via dbus or via "xpra control".
ie:
xpra control :1 set-lock auto xpra control :1 set-sharing off
Unfortunately, this can have undesirable side effects since we don't yet communicate the changes to the client: #1676
Very nice - noted and closing.
We could improve the UI for this a bit: #1690
r17804 updates the system tray if the "sharing" or "lock" options have been changed on the server.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1368