On 1/18/07, Francois Piette <[EMAIL PROTECTED]> wrote:
> It is totally incorrect. Such a loop will prevent any event from occuring
> and the state of the component will not change since it is blocked.
Thanks!
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://w
> When I want to terminate the thread normally or when I force it to
> terminate I call the THttpCli.Abort method. How can I insure that the
> THttpCli component is indeed aborted before freeing it and ending the
> thread?
>
> Right now I do:
> HTTP.Abort;
> while HTTP.State<>httpReady do
> Sleep
I think my problems may have been with the receive stream being freed
before the THttpCli was aborted. Kind of like removing the road before
telling your car to stop.
I am continuing to test, but was curious what other people do when
THttpCli absolutely must be stopped before doing anything else.
>I have a multi-threaded application that uses a dynamically created
> THttpCli synchronously. I know that ICS is normally used
> asynchronously, but I could not determine a good way to handle that
> with all the dynamically created threads I have to use for database
> access anyway.
>
> When I w
I have a multi-threaded application that uses a dynamically created
THttpCli synchronously. I know that ICS is normally used
asynchronously, but I could not determine a good way to handle that
with all the dynamically created threads I have to use for database
access anyway.
When I want to termina
