Throttling in ENet has always been done on a per connection basis. :)
The congestion metric is based on the length of a round trip time
between a host and a given peer, and the RTT metrics and throttle values
are stored in the peers themselves.
The issue is more one of quality of service: one connection hogging
bandwidth can cause the throttles of all other connections to go down
because the link overall is congested.
Lee
On 12/20/2010 05:38 PM, Jay Sprenkle wrote:
On Sun, Dec 19, 2010 at 6:49 PM, Lee Salzman <[email protected]
<mailto:[email protected]>> wrote:
Problem solved in one damned line of code. Oh, how blind I was. :(
-> :)
Thoughts?
Thanks for putting in the time to make enet better :) I'll patch my code.
I realize it's a much larger change than one line but I'd really like
to see throttling adjustable on a per connection basis. That would
provide a better mechanism to react to denial of service attacks. I
could at least attempt to throttle back the offending connection with
less affect on other connections.
It may be a better solution to handle this in the network firewall
code instead of enet. If anyone has any feedback on this I'd love to
receive it.
---
"The great thing about Object Oriented code is that it can make small,
simple problems look like large, complex ones."
_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss
_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss
