Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

a server event interface #625

Closed
totaam opened this issue Aug 3, 2014 · 10 comments
Closed

a server event interface #625

totaam opened this issue Aug 3, 2014 · 10 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Aug 3, 2014

Issue migrated from trac ticket # 625

component: core | priority: critical | resolution: fixed

2014-08-03 15:30:45: totaam created the issue


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.

@totaam
Copy link
Collaborator Author

totaam commented Aug 4, 2014

2014-08-04 09:03:16: totaam changed owner from antoine to sbennett

@totaam
Copy link
Collaborator Author

totaam commented Aug 4, 2014

2014-08-04 09:03:16: totaam commented


Implemented in r7116 (see commit message for details).

Try it with the new hidden command _monitor:

xpra _monitor :DISPLAY

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 connection
  • startup-complete: uuid when the client has received all the windows
  • connection-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 connection

and more..

@totaam
Copy link
Collaborator Author

totaam commented Aug 17, 2014

2014-08-17 15:23:32: totaam changed priority from major to critical

@totaam
Copy link
Collaborator Author

totaam commented Aug 17, 2014

2014-08-17 15:23:32: totaam commented


Should be closed for v0.14.x, raising to critical.

@totaam
Copy link
Collaborator Author

totaam commented Aug 19, 2014

2014-08-19 04:34:53: totaam commented


Should be closed against milestone 0.14

@totaam
Copy link
Collaborator Author

totaam commented Aug 19, 2014

2014-08-19 06:07:03: sbennett changed status from new to assigned

@totaam
Copy link
Collaborator Author

totaam commented Oct 27, 2014

2014-10-27 17:52:34: totaam commented


Bump!

@totaam
Copy link
Collaborator Author

totaam commented Feb 13, 2015

2015-02-13 04:50:32: totaam commented


Unless anything is still missing, please close.

@totaam
Copy link
Collaborator Author

totaam commented Mar 21, 2015

2015-03-21 17:41:00: antoine changed status from assigned to closed

@totaam
Copy link
Collaborator Author

totaam commented Mar 21, 2015

2015-03-21 17:41:00: antoine set resolution to fixed

@totaam totaam closed this as completed Mar 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant