🚀 go-pugleaf

Bob,

I follow what you are saying but in this case I dont think thats the 
problem.

I write events to a log file (most of which I stripped out of the example 
code to simplify things.
The log file shows that I send the request for data an 10-12 seconds later 
the program times out with the message:

"No data recieved for 10 counts"

I can then see it going into the MyDisconnect function and calling the 
disconnect.
I write a log message right before and directly after the actual diconnect 
call and the log file shows the one before it and nothing after that.

In fact I have added another timer to the form that simply fires once a 
second and writes the state of the original timer to the log file, eg 
whether it is enabled or not.
Even this extra timer stops at this point.

I originally had a similar problem when I tried to disconnect from inside 
the OnDataAvailable event.
Looking in the delphi source for the Telnet component I figured out that 
this was causing a deadlock as the mainthread was waiting for the connection 
thread to terminate which was stuck inside the OnDataAvailable method also 
waiting for itself to terminate.

This seems to be something similar, except that the disconnect is now no 
longer being called in the OnDataAvailable method but rather in the timer.

It seems as if the Telnet component recieves the incoming data, but for some 
reason gets stuck and doesnt call the OnDataAvailable method.  When I then 
try and disconnect the disconnect method waits for the connection thread to 
terminate (which is stuck) so it never returns, thus locking up the main 
thread (from which the disconnect was called).

A work-around for this *might* be to spawn my own thread in which to call 
the disconnect.
But then I will have the problem of killing this new thread if it should get 
locked up with the telnet component.
And of course it could introduce extra complexity in my own code with shared 
data and critical sections etc. etc.

Make any sence?  Or I am on the wrong track here completely?

Andre'




"Bob Gonder" <notbg@notmindspring.invalid> wrote in message 
news:adsdf2dk8k4s0tefv5r49fi67ghjs6rlmt@4ax.com...
> Andre' Burke wrote:
>
>>I would greatly appreciate any advice.
>
> 2 suggestions:
>
> 1) Don't rely on _finally catching a return;
> There is a "bug" with _finally and return.
> In this case, if it hits, your timer stays Off.
>
> 2) Restucture your code
> If "state" is a state machine, it might be clearer to use a
> switch(state) with the cases in state-order.
> Added benefit: breaking out of the switch allows you to drop to the
> _finally and timer-enable, no internal returns needed.
>
> At the very least, restart the timer before every return statement,
> and see if things don't improve.
>