Code Forums - View Single Post

TheSheep · 06-04-2005, 12:41 PM

Thanks for the suggestion; I'll certainly look at the possibility but I'd expect it to receive the termination message in that case and respond to it.

Unfortunately it's not exactly easy to post up the code since it's spread between about 5 different modules. As an outline, the server and client are both running timers and checking receiving every 1/2 second, and are 1/4 second out-of-sync with each other (I figured this would be far more practical than some sort of negotiation since the max possible message size is 1KB). Each application receives the message, processes it (which only consists of quick memory I/O) and sends its reply.

I thought maybe there's some feature of the sockets API that I'm missing altogether. This is my first ever sockets program so kinda lends itself to disaster. Does initialising the API or socket allow the API to buffer input until it's retrieved or something?

06-04-2005, 12:41 PM	#3 (permalink)
TheSheep Registered User Join Date: Mar 2005 Location: UK Posts: 11	Thanks for the suggestion; I'll certainly look at the possibility but I'd expect it to receive the termination message in that case and respond to it. Unfortunately it's not exactly easy to post up the code since it's spread between about 5 different modules. As an outline, the server and client are both running timers and checking receiving every 1/2 second, and are 1/4 second out-of-sync with each other (I figured this would be far more practical than some sort of negotiation since the max possible message size is 1KB). Each application receives the message, processes it (which only consists of quick memory I/O) and sends its reply. I thought maybe there's some feature of the sockets API that I'm missing altogether. This is my first ever sockets program so kinda lends itself to disaster. Does initialising the API or socket allow the API to buffer input until it's retrieved or something?