Currently the spice server emits the events connected, initialized and disconnected on a per TCP connection basis. Which results in multiple events for each spice channel. To make the life easier to ignore invalid connection attempts and to be able to distinguish real disconnects from live/seamless migration related disconnects. The goal is to basically have 'sessions' where the events are published per session and not per channel. e.g. when the main channel has been intialized the session event would start and when it gets disconnected due to any other reason than a live/seamless migration, then it would emit an event that the session ended. Thanks :-)
Mailing list request for this http://lists.freedesktop.org/archives/spice-devel/2015-September/022077.html
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/spice/spice-server/issues/13.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.