xpra icon
Bug tracker and wiki

Changes between Initial Version and Version 1 of Ticket #540


Ignore:
Timestamp:
03/21/14 00:50:17 (5 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #540 – Description

    initial v1  
    66* it may also be useful to have those same event hooks on the server side: knowing that something is broken with the network would be useful in the logs and we could prevent unnecessary/unhelpful changes to speed,quality and batch settings when network problem occur
    77* optional: when new interfaces come up, do we want to start publishing our mdns record on them?
     8* if the client suspends then resumes, maybe we want to keep the connection alive longer (from #492):
     9{{{
     102014-03-20 13:42:21,933 system is suspending
     112014-03-20 13:42:24,628 server is not responding, drawing spinners over the windows
     122014-03-20 13:43:40,279 system resumed, was suspended for 0:01:18
     132014-03-20 13:43:40,358 WM_TIMECHANGE: time change event: 0 / 0
     142014-03-20 13:43:40,390 server ping timeout - waited 60 seconds without a response
     152014-03-20 13:43:41,920 Connection lost
     16}}}
     17In this case, the sleep was longer than 60 seconds, but if the TCP connection can be kept alive, why not keep it? (just suspend most of the work on the server until the underlying TCP connection breaks?)
    818
    919Some links: