Age | Commit message (Collapse) | Author |
|
Co-authored-by: Arvid Norlander <[email protected]>
|
|
|
|
|
|
On connect the MTU sent by the client gets stored and sent back
unchanged if within minimum and maximum of the protocol. Then on verify
connect a test is done if the returned MTU is smaller than the current
MTU and if so gets adjusted. So as long as the MTU is within boundaries
only the client specified MTU is relevant.
This patch adds a check for smaller MTU on server side.
Signed-off-by: Ralph Sennhauser <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Return 0 instead of -1 on enet_protocol_receive_incoming_commands when nothing received.
This allows the Service loop to continue running and not return an error when there is nothing to do with the socket receive.
From debugging I found sometimes the enet_protocol_receive_incoming_commands returns -1 because simply nothing happened in the 256 for loop.
Other functions like enet_protocol_send_outgoing_commands return 0 when nothing happened.
|
|
|
|
|
|
|
|
|
|
|
|
limits are disabled, but not both
|
|
|
|
already exists
|
|
buffer space
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
enet_socket_connect() shouldn't fail with non-blocking sockets.
Removed unused variable.
Sanity check for possible NULL dereference reported by clang's static…analysis.
Added an interface to shutdown().
Fixed typo in the comments.
|
|
|
|
|
|
1.3.4 release prep
|