[Spice-devel] [PATCH spice-server 06/10] reds: disconnect the session when an essential channel is disconnected

[bigclouds]

Yonit Halperin:
1.you mean the patch is for client?
2.where is the code in client side from which i can get channel's status. if it is disconnected, i close client throught client's code.
3.i notice that there is 'session' .   for client what does it mean?  whether cleaning(close) session means close client?
 
thanks





At 2013-05-22 02:52:14,"Yonit Halperin" <yhalperi at redhat.com> wrote:
>On 05/20/2013 10:39 PM, bigclouds wrote:
>> 1.is there a solution now?
>> server may disconnect some of spice channels, but client does not
>> reconnect , how to do with this?
>> close client  or let client reconnect?
>
>This patch hasn't been pushed. We concluded that the policy of 
>disconnecting the client when one of the channels shutdown should be on 
>the client side.
>> 2.
>> where is the code from which we can get socket signal(error,EPIPE..)
>> when channel disconnected.
>
>For most of the channels, you can find it in red_channel.c . For the 
>sound and record channels, it is in snd_worker.c (snd_send_data, 
>snd_receive).
>
>> thanks
>>
>>
>>
>> 在 2013-05-08 23:57:54，"Marc-André Lureau" <marcandre.lureau at gmail.com>
>> 写道：
>>
>>
>>     On Wed, May 8, 2013 at 5:03 PM, Yonit Halperin <yhalperi at redhat.com
>>     <mailto:yhalperi at redhat.com>> wrote:
>>
>>         I can live with that. Maybe we should add to spice-gtk a user
>>         notification when a channel gets suddenly disconnected.
>>
>>
>>
>>     Since UI don't share same designs, the best place for such dialog
>>     is virt-viewer (or Boxes etc).
>>
>>     We already have a similar channel-event handler for the main channel
>>     in virt-viewer-session-spice.c, this can easily be extended to cover
>>     other disconnections
>>
>>     --
>>     Marc-André Lureau
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/spice-devel/attachments/20130522/502ee4e2/attachment.html>