<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [feature-request] Spice Server: Introduce session started/ended events"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91085">91085</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[feature-request] Spice Server: Introduce session started/ended events
</td>
</tr>
<tr>
<th>Product</th>
<td>Spice
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>server
</td>
</tr>
<tr>
<th>Assignee</th>
<td>spice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>evilissimo@redhat.com
</td>
</tr></table>
<p>
<div>
<pre>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 :-)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>