#625 closed task (fixed)
a server event interface
Reported by: | Antoine Martin | Owned by: | Scott Bennett |
---|---|---|---|
Priority: | critical | Milestone: | 0.14 |
Component: | core | Version: | trunk |
Keywords: | Cc: |
Description
So the server can expose important session events:
- new clients connecting
- client disconnected
- lost connection events
- first UI event (sent when the first window or tray is sent to the client
- startup complete (sent when all the windows and trays have been sent to the client after it connects - can precede first UI event if there are no windows to forward)
- server exit events (shutdown, etc)
If might make sense to expose this via dbus, but the easiest thing to do initially is probably to just add this interface to xpra's own channel.
Change History (8)
comment:1 Changed 8 years ago by
Owner: | changed from Antoine Martin to Scott Bennett |
---|
comment:2 Changed 8 years ago by
Priority: | major → critical |
---|
Should be closed for v0.14.x, raising to critical.
comment:4 Changed 8 years ago by
Status: | new → assigned |
---|
comment:7 Changed 7 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:8 Changed 16 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/625
Note: See
TracTickets for help on using
tickets.
Implemented in r7116 (see commit message for details).
Try it with the new hidden command
_monitor
:If that works for you, let me know what other events we can add, the only events you will get right now are:
handshake-complete
when we accept a connectionstartup-complete: uuid
when the client has received all the windowsconnection-lost: uuid
when the client connection is lost (for whatever reason)We could add:
first-ui-event
(though at the moment this one is done client side, so the logic would have to be replicated server side, no biggie)disconnect
events so we know when the client exited cleanly rather a lost connectionand more..