🚀 go-pugleaf

longshot wrote:

>Are you sure there is no way to force the packets to be send separately?

I use WinSock commands (not Indy), and found that the following code
made my c/s sessions go quicker as the server sends (usually) small
packets and sometimes waits for a response from the client.
Without this, there seemed to be a delay as the socket waited for more
data to make a worthy-sized transmission packet. So the server would
be waiting for it's socket to timeout and send, and then the
round-trip delay....it all added up to a slow user experiance.

/* one of these works, don't know yet which */
setsockopt(ClientOutSocket,SOL_SOCKET,TCP_NODELAY,(char*)&t,sizeof(t));
setsockopt(ClientOutSocket,IPPROTO_TCP,TCP_NODELAY,(char*)&t,sizeof(t));

>It really would save me a lot of work 

As Remy said: No, it wouldn't.
You still need to recreate received packets correctly.
The only thing this would get you is better response time.

>and also i don't like my packets to
>stick together when there is lag and have this strange behaviour.

Then you could impliment full duplex communication where the server
waits for an acknowledgment from the client for every packet. But
then, you would need to add some sort of timeout so the server doesn't
lock up on a lost packet.

>Also i am building a server app, that means lots of communication, thus
>Sleep(200); 's are extremely unwanted.

If each client has it's own server thread, then that should not be a
concern.