Re: [twsocket] Should next ICS version support anything before Delphi XE ?
Hi, I have some old projects on D2006 that get tweaked from time to time. Using V6? No major new development. Anything new is now using XE. ...Andy On 28/03/2012 19:59, François Piette wrote: Hi ! I’m planning the next ICS version… Being unable to use any features added to Delphi in the last 10 years is very restricted. Maybe we need to cease support for old Delphi versions ? Of course ICS V5 and V7 will remains available however, the only changes will be bug fixes. What do you think ? Please keep your answer as short as possible, I just want to have an idea about how many of you are still using an old Delphi version. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) 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 -- 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
[twsocket] TWSocket closing after every transaction with external HTTP server
Hello, I have a Delphi 6 application that talks to an external device that acts as an HTTP server. I am using the ICS TWSocket components for this application. I open up a socket to talk to the device and handle the necessary header and body crafting to talk to the server. In other words, I am not using the ICS HTTP client component but using the lower level TWSocket component and handling the necessary HTTP handshaking myself. The headers I craft and send to the external device have the keep-alive flag set to TRUE. On my system, after I send anything to the external device, the connection will stay open continuously and will not close until approximately 30 seconds of inactivity occurs (30 seconds where I don't make any requests of the external device as an HTTP server). I don't know if the external device closes it or if Microsoft Windows does it. But the important point is that normally I can do multiple sends and the connection will stay open until I send nothing for about 30 seconds. This works fine and is what my code expects. However, on some of my users systems the socket is closing after every send. I do have code that checks for a closed socket and attempts a reconnect to the external device if necessary, but does not expect to have to do a reconnect with each transaction. My questions are: Is there a system setting for sockets that might be causing this anomalous behavior on some users systems? If so, are there Windows API function calls I can use to query the offending parameter and then set it to the expected close on 30 seconds of inactivity instead of with each transaction? If so, can I, or how do I do it in a manner that will not adversely affect any other programs running on the users system? Thanks, Robert -- 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
Re: [twsocket] TWSocket closing after every transaction with external HTTP server
Hello, How do you now socket has been closed ? have you done some tcpdump compare between wroking and non-working system ? May be some users are going out thru a proxy that remove the keep-alive ? regards. r Hello, r I have a Delphi 6 application that talks to an external device that acts as an HTTP server. I am using the ICS TWSocket components for this application. I open up a socket to talk to the device r and handle the necessary header and body crafting to talk to the server. In other words, I am not using the ICS HTTP client component but using the lower level TWSocket component and handling the r necessary HTTP handshaking myself. r The headers I craft and send to the external device have the keep-alive flag set to TRUE. On my system, after I send anything to the external device, the connection will stay open continuously and r will not close until approximately 30 seconds of inactivity occurs (30 seconds where I don't make any requests of the external device as an HTTP server). I don't know if the external device closes r it or if Microsoft Windows does it. But the important point is that normally I can do multiple sends and the connection will stay open until I send nothing for about 30 seconds. This works fine r and is what my code expects. r However, on some of my users systems the socket is closing after every send. I do have code that checks for a closed socket and attempts a reconnect to the external device if necessary, but does r not expect to have to do a reconnect with each transaction. r My questions are: r Is there a system setting for sockets that might be causing this anomalous behavior on some users systems? r If so, are there Windows API function calls I can use to query the offending parameter and then set it to the expected close on 30 seconds of inactivity instead of with each transaction? r If so, can I, or how do I do it in a manner that will not adversely affect any other programs running on the users system? r Thanks, r Robert r -- r To unsubscribe or change your settings for TWSocket mailing list r please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket r 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
Re: [twsocket] TWSocket closing after every transaction with external HTTP server
Hello Dod, 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. Robert. --- On Thu, 4/5/12, Dod do...@yahoo.com wrote: From: Dod do...@yahoo.com Subject: Re: [twsocket] TWSocket closing after every transaction with external HTTP server To: ICS support mailing twsocket@elists.org Date: Thursday, April 5, 2012, 5:36 AM Hello, How do you now socket has been closed ? have you done some tcpdump compare between wroking and non-working system ? May be some users are going out thru a proxy that remove the keep-alive ? regards. r Hello, r I have a Delphi 6 application that talks to an external device that acts as an HTTP server. I am using the ICS TWSocket components for this application. I open up a socket to talk to the device r and handle the necessary header and body crafting to talk to the server. In other words, I am not using the ICS HTTP client component but using the lower level TWSocket component and handling the r necessary HTTP handshaking myself. r The headers I craft and send to the external device have the keep-alive flag set to TRUE. On my system, after I send anything to the external device, the connection will stay open continuously and r will not close until approximately 30 seconds of inactivity occurs (30 seconds where I don't make any requests of the external device as an HTTP server). I don't know if the external device closes r it or if Microsoft Windows does it. But the important point is that normally I can do multiple sends and the connection will stay open until I send nothing for about 30 seconds. This works fine r and is what my code expects. r However, on some of my users systems the socket is closing after every send. I do have code that checks for a closed socket and attempts a reconnect to the external device if necessary, but does r not expect to have to do a reconnect with each transaction. r My questions are: r Is there a system setting for sockets that might be causing this anomalous behavior on some users systems? r If so, are there Windows API function calls I can use to query the offending parameter and then set it to the expected close on 30 seconds of inactivity instead of with each transaction? r If so, can I, or how do I do it in a manner that will not adversely affect any other programs running on the users system? r Thanks, r Robert r -- r To unsubscribe or change your settings for TWSocket mailing list r please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket r 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 -- 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
Re: [twsocket] TWSocket closing after every transaction withexternal HTTP server
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
Re: [twsocket] TWSocket closing after every transaction withexternal HTTP server
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
Re: [twsocket] TWSocket closing after every transaction withexternal HTTP server
Hello, Which webcam model ? how many users are connected at same time on it ? is there one or mutiples cameras ? r Hello Arno, Sending the Keep-Alive header line doesn't guarantee a HTTP server keeps the connection alive. r 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. r Robert. r --- 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 r -- r To unsubscribe or change your settings for TWSocket mailing list r please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket r 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
Re: [twsocket] TWSocket closing after every transactionwithexternal HTTP server
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
