🚀 go-pugleaf

"Omar Zelaya" <ozelaya2010@hotmail.com> wrote in message
news:46fc0255$1@newsgroups.borland.com...

> I allready tried that, but i have some problems with non-windows
> tcp clients(i.e. Mainframes) on Indy10(client gets a timeout)

Then the client is likely not sending any data to begin with.  There is
nothing in the code I have given you that can raise an timeout exception.

> going to make more research to find out wich specifc ones doesnt
> work with Indy10.

TCP is TCP regardless of whether you use Indy 9 or 10.  If the data being
sent is the same, then Indy 10 should be working fine for you.

> With Indy 9 works with no problems.

You shouldn't really be checking for Connected() at all, in either 9 or 10.
Let Indy raise an exception when you try to read from a socket that has been
closed.  That will notify the server to shut down the thread for that
connection.

Try this instead:

    ClientSession = (TClientSession*) AContext->Data;
    AContext->Connection->IOHandler->CheckForDataOnSource(IdTimeoutDefault);
    NewData = AContext->Connection->IOHandler->InputBufferAsString();
    if( (NewData != "") && (ClientSession != NULL) )
        ClientSession->NewDataReceived(NewData);


Gambit