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. Robert. --- On Thu, 4/5/12, Arno Garrels <arno.garr...@gmx.de> wrote: > From: Arno Garrels <arno.garr...@gmx.de> > Subject: Re: [twsocket] TWSocket closing after every transaction withexternal > HTTP server > To: "ICS support mailing" <twsocket@elists.org> > Date: Thursday, April 5, 2012, 8:18 AM > robertoschler wrote: > > > I know the socket is closed because the TWSocket > OnSessionClosed() > > event fires. There are no proxies because the > external device is on > > the Intranet (same router and network) as the PC. > It's a local peer > > connection. > > Sending the Keep-Alive header line doesn't guarantee a HTTP > server > keeps the connection alive. Obviously there's some idle > timeout > configured at the server side. May be you can issue some > dummy > request in intervalls in order to work around this. However > some HTTP servers prevent this as well by limiting the > maximum > number of requests per 'session'. > > -- > 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 > -- 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
