forum.vdsworld.com

Hortalonus

Can anyone shed any light on why some TCP messages sent between server and client would arrive without any data?

For example:
- the client sends authentication info to the server
- the server recieves the info and replys with good guy/bad guy message
- the ONMESSAGE event is triggered but the message is blank

This even happens when testing on the loopback of my NIC so I know it's not losing the data on the network. It seems to be pretty random because it doesn't ever happen with specific messages and it doesn't happen very often.

Question

How would one implement some redundancy so if a message is not recieved correctly, the server or client would resend the message?

Garrett · Posted: Fri Sep 20, 2002 2:34 pm Post subject:

I would implement a successive numeric message ID system. Both client
and server would send a numeric id with each and every communication.
Maybe an 8 or 9 digit number starting from 00000001 and increment by
one with each communication.

Both client and server keep track of the numbers, and if a number is
missing, then you know a message has been lost.

When the numbers have reached 99999999 then start the numbers over
again.

-Garrett

Hortalonus · Posted: Fri Sep 20, 2002 4:22 pm Post subject:

Hey Garret!

That would probably work well. And for multiple connections I could include a connection identifier in the message ID. Thanks!