This is because spice relies on default tcp behaviour. IMO the only
alternative is to have some heartbeat in main channel that would
initiate client disconnection if the connection is interrupted.
Spice behaviour is analogous to e.g. IRC behaviour while the latter is
similar to e.g. XMPP/Jabber (o
hi,
i unplug cable for 30 minutes, server are not aware of client's
disconnection, i think it is a defect.
whether keeping a disconnect socket depend on how much work you can save in
order to recover disconnected socket. even you delay to disconnect cahnnels
, but finally you have to disc
On Tue, 2013-05-14 at 07:18 -0400, Marc-André Lureau wrote:
>
> Hi
>
> - Mensaje original -
> >
> > We don't have any keep alive.
>
> Do you know if there is a reason? (perhaps I am missing something obvious)
Not really. I mean, what's the down side, a tiny bit of bandwidth /
wakeups?
Hi
- Mensaje original -
>
> We don't have any keep alive.
Do you know if there is a reason? (perhaps I am missing something obvious)
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/s
On Tue, 2013-05-14 at 17:38 +0800, bigclouds wrote:
> hi,all
> look at the output of netstat, it is after at least 30minutes i
> un-plug cable.
> how to make server know client's disconnect and disconnect
> channels(clean channels).
>
>
> tcp0 0 192.168.5.240:5903 192.168.5
hi,all
look at the output of netstat, it is after at least 30minutes i un-plug cable.
how to make server know client's disconnect and disconnect channels(clean
channels).
tcp0 0 192.168.5.240:5903 192.168.5.163:60029
ESTABLISHED 31315/qemu-kvm
tcp0
