MasterClient times-out sending large data
Options
I'm occasionally sending large amounts of binary data to other clients. The data is broken up into smaller packets, sent, and then reassembled on the client.
This works fairly well, but as I increase the lag the MasterClient times-out. I've tried varying the size of the packets, but that's not working. Sending a 200KB of data with a simulated lag of 100ms (rtt: 350ms) works. When I increase the data to 335KB the MasterClient times-out.
I am almost certainly filling up the buffer and being disconnected (DisconnectByServerLogic). Is there a way to check the status of the buffer to wait for it to clear before shoveling more things in?
Any suggestions?
This works fairly well, but as I increase the lag the MasterClient times-out. I've tried varying the size of the packets, but that's not working. Sending a 200KB of data with a simulated lag of 100ms (rtt: 350ms) works. When I increase the data to 335KB the MasterClient times-out.
I am almost certainly filling up the buffer and being disconnected (DisconnectByServerLogic). Is there a way to check the status of the buffer to wait for it to clear before shoveling more things in?
Any suggestions?
0
Comments
-
DisconnectByServerLogic means that most likely the buffer in there is overflowing and causing an issue.
Sadly, it's not possible to find out the state of the buffer. Neither in client, nor server.
If you run the server yourself, you can increase the buffers. If you do run them, please ask in the Server forum for details.
Thanks.0
