Re: Socket behavior change from 6.5 to 6.6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Fri, Jan 16, 2015 at 12:21 PM, Warren Young <wyml@xxxxxxxxxxx> wrote:
>
> A different fix is to exploit the real-time nature of video camera imagery: if your Python app goes more than a second without receiving an image frame, it can presume that the DOS box has disappeared again, and drop its conn.  By the time the DOS box reboots, TIME_WAIT may have expired, so the DOS box might reconnect without a problem.
>

Normally if you care about knowing if the other end of a connection is
gone you could enable keepalives on the socket, but I think you still
don't find out until you try to write to it.

-- 
   Les Mikesell
     lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux