🚀 go-pugleaf

"Andre' Burke" <no.spam@spam.no> wrote in message
news:44fd6bbc@newsgroups.borland.com...

> From looking at the IdTelnet.pas file, it would seem that if I were to
call
> the Disconnect method from inside my main thread while the OnDataAvailable
> is busy within the connection's thread, that the main thread would block
> until the connection thread was terminated, since the Disconnect method
> calls Terminate for the thread and then does a waitfor on it.

When the ThreadedEvent property is False, OnDataAvailable is triggered via a
call to TThread::Synchronize().  Synchronize() requires the main thread to
reply to the request, so the main thread can't be fully blocked, or else the
thread will also be blovked.  Fortunately, TThread::WaitFor() does allow
Synchronize() calls to finish their work.  So even if Disconnect() (and thus
TThread::WaitFor()) were called in the context of the main thread,
TIdTelnet's reading thread should still be able to terminate cleanly and
then release WaitFor() from its waiting.  The only time that would not
happen is if your OnDataAvailable event handler is performing operations
that require the main message queue (which is blocked), in which case you
will have to call Application->ProcessMessages() in your code.


Gambit