3 ms·
That doesn't quite provide the same experience, does it? For something like a scoreboard you don't want the message to be discarded once any packet loss is det
by crote 2y ago
That doesn't quite provide the same experience, does it?
For something like a scoreboard you don't want the message to be discarded once any packet loss is detected. As long as message N is the most recent one, message N should be retried until it succeeds. You just want to stop retrying N once N+1 becomes available - or ideally even successfully delivered.
- swiftcoder 2y agoIn a game context, where we're spewing state updates out 10-60x per second, there is always a newer packet in flight already, so discard-on-loss produces the same result. In your scoreboard example, you probably just want an actually reliable stream for that - it's not like scores are rolling in so fast that it's beneficial to deal with it as unreliable.