Wont go after 1st if

adr · February 14, 2008, 1:00pm

Manakel:

it can grossly work.

You just have to remember to keep track of the figures from both side
on client and on server.

when you send a message from Ci to S, your message could have in the header those 2 informations:Rci,Sci (last message received by client i, last message sent by client i)
and server keep it’s own version of this information.

This work well for lost message but not for out of order message.
In this case you may have to aknowledge (ACK or NACK) specific message number by piggybacking their ID on message sent back (ex from server to Client, you acknowledge reception of message from client to server)

Even with this you still have the issue that at any time, your set of message availabe on the server or on the client is not warranted to be complete and ordered.
So if you need causality then you need to poll the set in a specific way.

Basically you make an UDP Protocol with possibility to send order and / or reliable packet.
This would be RUDP (but linux only)
Or Enet (C only, small and efficient,used in sauerbraten engine) or Raknet (CPP / partial incomplete binding for python, feature rich and mostly efficient ).

For most game, TCP could be a valuable first choice (if not FPS game).

lol, ok x.x; I guess I have to rewrite my code for TCP now o.o;