TCPObject trashes outgoing packets.
by Stefan Lundmark · in Torque Game Engine · 11/05/2006 (12:51 pm) · 0 replies
What?
TCPObject trashes outgoing packets if too many are sent at once. To reproduce, place a for loop and send one packet in each iteration of the loop. One packet will be sent, and the others won't.
Is this because the TCP Window gets full? After one packet? Net::sendToSocket() is called but the packets never go out and I have not been able to fetch the error messages yet.
TCP gurus out there, any ideas?
The error message.
The error message returned is 10053 on each packet except the first one. Looking up 10053 on the net gives this:
So that makes sense, since the packet never reaches the receiver. Question is why.
TCPObject trashes outgoing packets if too many are sent at once. To reproduce, place a for loop and send one packet in each iteration of the loop. One packet will be sent, and the others won't.
Is this because the TCP Window gets full? After one packet? Net::sendToSocket() is called but the packets never go out and I have not been able to fetch the error messages yet.
TCP gurus out there, any ideas?
The error message.
The error message returned is 10053 on each packet except the first one. Looking up 10053 on the net gives this:
Quote:
TCP/IP scenario: A connection will timeout if the local system doesn't receive an (ACK)nowledgement for data sent. It would also timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will eventually timeout if a FIN is not returned).
So that makes sense, since the packet never reaches the receiver. Question is why.
About the author
