🚀 go-pugleaf

"mike" <mfbrowne@earthlink.net> wrote in message
news:41f01cbc@newsgroups.borland.com...

> Ok I understand what you have indicated, but now I am confused as
> to how I would implement the reading of the data. Would I simply use
> a timer in which my WinSocketStream Wait ForData() is located.

You missed the point I was trying to make earlier.  You only need to use a
thread/timer when you want to do other things while waiting for data to
arrive.  If you are sending data and then expecting a response to come back
immediately, you don't need to use a thread or timer at all.  Just read
immediately after writing, ie:

    TWinSocketStream *Stream = new TWinSocketStream(ClientSocket1->Socket,
5000);
    Stream->Write(SomeData, DataSize);
    while( !Stream->WaitForData(1000) ) Sleep(50);
    Stream->Read(SomeBuffer, SomeSize);
    //...

> If I understand correctly the WaitForData() would stall all other
> operations until such time as data actually was received or it timed
> out.

Only if you are using the socket in the same thread as the other operations.

> The application itself is required to send and receive data based upon
> the user making choices through button clicks and so forth. In this type
> of situation would I be better to use a thread as I don't know when or
> whaic type of data will be received from the server.

If you do not know when data will arrive, and/or the received data is
arriving unsolicited, then yes, use a thread for the reading.


Gambit