You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although non-blocking network operations are often preferred in gamedev, there are also plenty of times it's easier (and more CPU efficient) to use the operating systems designated blocking receive mode instead of while looping on a receive, especially if it's in a designated child thread.
I've started working on a PR that would add SetSocketBlockingMode and GetSocketBlockingMode (with nonblocking mode still the default), but I wasn't sure if that's the direction this library is going in. What do you experienced SDLers think?
The text was updated successfully, but these errors were encountered:
Although non-blocking network operations are often preferred in gamedev, there are also plenty of times it's easier (and more CPU efficient) to use the operating systems designated blocking receive mode instead of while looping on a receive, especially if it's in a designated child thread.
I've started working on a PR that would add
SetSocketBlockingMode
andGetSocketBlockingMode
(with nonblocking mode still the default), but I wasn't sure if that's the direction this library is going in. What do you experienced SDLers think?The text was updated successfully, but these errors were encountered: