Hey,
Does enet implies any congestion control algorithm or the client which uses the library is responsible to do so ?
By looking at the following method:
enet_host_create (const ENetAddress * address, size_t peerCount, size_t channelLimit, enet_uint32 incomingBandwidth, enet_uint32 outgoingBandwidth)
The incomingBandwidth and outgoingBandwidth can be dynamic if we are over the internet, so for the sake of example, if my connection is 100 mb/s and I set the bandwidth to be 200 mb/s, I will simply suffer from packet loss ? and if the client is responsible for the congestion control, does enet provide the required statists that from it the client can learn and update the incoming/outcoming bandwidth ?
Hey, Does enet implies any congestion control algorithm or the client which uses the library is responsible to do so ?
By looking at the following method:
enet_host_create (const ENetAddress * address, size_t peerCount, size_t channelLimit, enet_uint32 incomingBandwidth, enet_uint32 outgoingBandwidth)The incomingBandwidth and outgoingBandwidth can be dynamic if we are over the internet, so for the sake of example, if my connection is 100 mb/s and I set the bandwidth to be 200 mb/s, I will simply suffer from packet loss ? and if the client is responsible for the congestion control, does enet provide the required statists that from it the client can learn and update the incoming/outcoming bandwidth ?