🚀 go-pugleaf

mike wrote:
> I have been trying to figure out how to properly write a blocking client
> application and have some basic questions.
> 
> 1- Is there an example around that I could study to see how this is done.

You can start at:
http://bdn.borland.com/article/0,1410,26276,00.html
It is a blocking TServerSocket and a non-blocking TClientSocket.
You can use the blocking code for the server for the client too.
Be sure to read the "Add or View comments" at the bottom of that page.

> 2- From what I have read I seem to understand the following, but I am not
> sure if I am correct or not.
> 
> - Set the Client Socket to Blocking.

ClientType ctBlocking

> - Once I have established a connect to the server, create my own thread that
> will do my reading of any data being received. I do this using the
> WinSocketStream and the method WaitForData()
> - from this thread then process the message.

You have to consider the type of client that you gonna
make. Wil the server only send data to the client after a request from the
client ?

Does your client application do other things then just communicating
with a server?

> 3- For writing to the socket, do I need to have a separate thread.

No.

> I am a little confused on how to put all this together so if someone has a
> sample or could help me lay it out  it sure would help.

Please have a look first.

Hans.