Benjamin Saunders
Benjamin Saunders
Another concern that bears some thought is the hazard of a CPU DoS attack. A peer can exert substantial control over the number of ranges in these fields, and the...
https://github.com/quinn-rs/quinn/issues/2422 will also improve some B-tree operations, which might tilt the balance.
That should work, yeah, at the cost of a little more complexity and boilerplate.
IMO this should be present on every `Event`. A simple approach is to add the timestamp as an extra argument to the `run` closure. Alternatively, we could introduce something like...
That's correct.
Given that games routinely render with frame intervals much larger than a millisecond, I'm not sure I agree that 1ms granularity is categorically "nowhere near useful"; it is trivially much...
I wouldn't describe rendering as "blocking work", but on e.g. macOS it *must* happen on the same thread that handles input, and regardless of platform games tend to be built...
> Performance I see no reason to expect that these changes present any performance hazard, and I'm satisfied with the smoke-testing you've done to check that assumption.
Something like the `UdpPollHelper` is absolutely necessary if we don't want boxing on every operation. I do suspect that, with enough effort, we might be able to get rid of...
> maintain a global map of configs keyed by each "unique" connection Why not a single global config?