LiteNetLib
LiteNetLib copied to clipboard
RevenantX
Blocking mode support for pollevents
It's a cleaner approach to continuously process the events for server. For a high loaded server, we do not have to make the thread sleep when it shouldn't For a low loaded server, where Thread Sleep is set to 15ms or similar, this will prevent possible scenarios where packets wait for the same duration without any additional performance penalty
In other words: If packets are sent every 1ms, this will ensure that the packets processed every 1ms aswell. If packets are sent every 15ms, then also this will ensure that the packets will be processed at the same interval. If no packets are received, then the poll thread will remain blocked.
So, uh... Why not take advantage of async instead of processing stuff on the update thread?
Edit: Like, Given the option, I would prefer not to handle network messages from my game server's update thread.
@sunkin351 this is not intended for multi threading. its a typical console based echo server use case scenario where you want to immediately respond back to any packet received without having to overshooting our cpu you can still use the good old Update method polling if you dont want to stick with this method :)
Just curious, what is your use case that you would need changes like this?
Any PCM signal. Application was VoIP in my case which needs a constant spacing
It's a cleaner approach to continuously process the events for server. For a high loaded server, we do not have to make the thread sleep when it shouldn't For a low loaded server, where Thread Sleep is set to 15ms or similar, this will prevent possible scenarios where packets wait for the same duration without any additional performance penalty
In other words: If packets are sent every 1ms, this will ensure that the packets processed every 1ms aswell. If packets are sent every 15ms, then also this will ensure that the packets will be processed at the same interval. If no packets are received, then the poll thread will remain blocked.
It is better to use UnsyncedEvents (or UnsyncedReceiveEvent) in this case
