robertoschler wrote: > Hello Arno, > >> Sending the Keep-Alive header line doesn't guarantee a HTTP >> server keeps the connection alive. > > True but in this case the external device is the same for all users. > It's a mobile web cam, same model and same firmware. That's whey I'm > wondering if it's an O/S issue.
Just to clarify, some clients are disconnected immediately after the device/server response has been received and some are not (only after 30 seconds idle timeout)? The device is not the same, but another one, however the same model and firmware? What do you mean by "the external device have the keep-alive flag set to TRUE"? HTTP keep-alive or TCP keep-alive? In order to figure out who closes the connection it helps to log communication between the peers with a network sniffer such as the free WireShark. -- Arno -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
