"Larry" <lchiasson@autoeurope.com> wrote in message
news:446e109c@newsgroups.borland.com...
> After each request is fullfilled, allocated critical sections
> are not destroyed, sometimes, not all the time.
Which requests are you referring to? Please be more specific. Since you
obviously can track the "leaks", where EXACTLY are they occuring?
> Also, the number of orphaned critical sections would vary (3, 4, 7, etc.).
Any Indy objects that create their own provate critical sections always make
sure to free them properly. The only "leaks" are in the 2 global critical
section objects that Indy can't free without causing crashes during unit
finalizations.
> Also, if the .Connect method call fails, how should be handled?
> Our current method of handling is to completely start over
> (release the allocated resources and call the function again)
> Or is it safe to just make the call again?
Yes, you can just make the call again.
> Since we currently the socket resources in the thread, I wonder
> if creating in the main thread would solve the orphaned CS mystery.
No.
Gambit
