| Dart Home | PowerTCP Web for ActiveX | Custom Development | Reply | PowerTCP Web for ActiveX Topics | Forums |
| Author | Forum: PowerTCP Web for ActiveX Topic: Forcing an Abort |
| User855 Posts: 4 Member Since: 03/12/01 |
posted March 12, 2001 9:39 AM In non-blocking mode I can't force an abort whilst the control is waiting for a response, e.g. after the 'get' method has been called. Is this by design - or is there a work-around? There is a timeout if no response is received when in non-blocking mode - can this be set programatically? |
Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted March 12, 2001 9:53 AM I'm not sure what you mean. The sample app uses Abort and seems to work OK for me. That's exactly what abort is for. Thanks, Tony Priest Dart Tech Support |
| User855 Posts: 4 Member Since: 03/12/01 |
posted March 12, 2001 12:49 PM Tony, I'm not sure whether the abort method is working as you would expect or not... the effect is as follows - set proxy and authentication - set control timeout to 0 - set URL - send GET request via get method - before GET request completes try to cancel request with abort method - after some seconds the control status confirms the abort has completed (or some timeout has occurred) What I'd like is that the abort method causes the control to stop waiting for a GET request response more quickly - typically this take 20-30s. As I'm running approx 10-20 instances of the control at once this can mean that, for example, application termination can take a long time. Hope that helps. --Shirley |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted March 12, 2001 12:52 PM The Abort method causes everything to stop immediately. This is eveidenced by starting a long download with the sample and clicking the Abort menu item. I'm not sure what you mean by "typically this take 20-30s" Thanks, Tony |
| User855 Posts: 4 Member Since: 03/12/01 |
posted March 12, 2001 1:08 PM The difference between your (working) example of abort that works immediately and my experience is that I am trying to abort BEFORE the target server has started responding. If I monitor progress via the status event I can see that the request lookup works but the connect doesn't happen - as you would expect if trying to connect to a URL that isn't contactable. If I try to abort whilst in this 'waiting for a connect' state the control hangs for some seconds before eventually releasing. This 'hang' sometimes prevents other program execution, sometimes it still allows it. In any case the program won't terminate until eventually the control returns from waiting. Hope that helps. --Shirley |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted March 12, 2001 1:24 PM I just used the following URL: http://192.168.0.245 which should cause the control to attempt connection for about 10 secs. When I pressed "Stop" it immediately returned. Please supply a URL that causes the problem you describe. Thanks, Tony |
| User855 Posts: 4 Member Since: 03/12/01 |
posted March 12, 2001 1:46 PM Tony, I tried to simulate the problem on a different machine to get more information and failed - the only difference being that the second machine uses Windows 98, whereas the problem is showing itself on a Windows 2000 machine. I'll investigate further and post some more specifics here. --Shirley |
| Reply | PowerTCP Web for ActiveX Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|