🚀 go-pugleaf

Thanks,

I allready tried that, but i have some problems with non-windows tcp 
clients(i.e. Mainframes) on Indy10(client gets a timeout), going to make 
more research to find out wich specifc ones doesnt work with Indy10. With 
Indy 9 works with no problems.

this is my for the Server Execute Method,
INDY 9:

ClientSession = (TClientSession*) AThread->Data;
  if (ClientSession != NULL)
   { if (AThread->Connection->Connected())
      { NewData = AThread->Connection->CurrentReadBuffer();
        if((NewData != "")
        ClientSession->NewDataReceived(NewData);
      }
   }

INDY 10
  ClientSession = (TClientSession*) AContext->Data;
  if (ClientSession != NULL)
   { if (AContext->Connection->Connected())
   { 
AContext->Connection->IOHandler->CheckForDataOnSource(AContext->Connection->IOHandler->ReadTimeout);
  NewData = AContext->Connection->IOHandler->InputBufferAsString();
  if (NewData != "")
     ClientSession->NewDataReceived(NewData);
   }
   }


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:46fa8f40$1@newsgroups.borland.com...
>
> "Omar Zelaya" <ozelaya2010@hotmail.com> wrote in message
> news:46f9bd49@newsgroups.borland.com...
>
>> I'm converting some code from Indy 9 to Indy 10, i use
>> CurrentReadBuffer() to wait and retrieve all data available
>> from the connection, now on Indy 10 which method or
>> methods can i use instead of CurrentReadBuffer() so i
>> can get the same functionality?
>
> Call the IOHandler's CheckForDataOnSource() and InputBufferAsString()
> methods, ie:
>
>    Connection.IOHandler.CheckForDataOnSource(Timeout);
>    Data := Connection.IOHandler.InputBufferAsString;
>
>
> Gambit
>
>