🚀 go-pugleaf

Dennis Cote <denniscote@gmail.com> wrote:
>Carlos Moreno wrote:
>> 
>> However, with the Indy HTTP control, it would seem like it does 
>> block everything --- I can't even grab the main window and move 
>> it;  everything freezes until *all* downloads are completed and 
>> the images do show up  (all of them simultaneously).
>> 
>> Any explanation for this?
>> 
>
>You probably need to add a TIdAntiFreeze component to your application.

Ok, this is shockingly interesting...  *AntiFreeze* component!! 
Whoh!  Seems like something taken from a Sci-Fi show!  :-)

Anyway, from the description I see in the docs, I still don't 
see how it could have anything to do with it.  Sure, the call 
to TIdHTTP::Get does block, as did the call to TNMHTTP::Get, 
but that's why I place the component in a separate thread, with 
low priority.

In the TIdAntiFreeze documentation, they say that if some of 
these blocking calls occur in the main Thread, then the GUI 
could block/freeze, and that the AntiFreeze component is useful 
to counter this effect. 

But that's the thing --- it's not in the main thread in my 
case.  Unless the HTTP control does make use of some global 
resource that in turn blocks the main thread?   (that would 
be a *major* worry, as that would seem to suggest that the 
component is inherently non-thread-safe?   Sounds strange, 
though...)


Thanks,

Carlos
--