- From: Michael Saunders <michael@amtec.com>
- Date: Tue, 08 Jun 1999 17:19:36 -0700
- To: www-lib@w3.org
The documentation HTReq.html documentation indicates that if I want to kill all requests I MUST use HTHost_killPipe. Currently my application checks for detects that the user wants to cancel the request while in the progress dialog callback. When I issue the HTHost_killPipe from within that callback it causes a segmentation fault "HTReader.c":201 within the HTReader_read function after returning from the call to my progress dialog callback. It appears that I am not allowed to call HTHost_killPipe from my callback because it pulls the rug out from under the library. My questions are: 1) From which callbacks should I be calling HTHost_killPipe to cancel a request that will not causing the library to perform a segmentation fault? Timer callbacks, progress callbacks, error callbacks, etc? 2) What steps should I perform to kill requests and still have the library in a sane state for subsequent requests at a later time? Thanks, Michael
Received on Tuesday, 8 June 1999 20:19:49 UTC