Are we sure we want to hardcode nonblocking mode for sockets?

[egnima]

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?

[MrOnlineCoder]

I personally support this, it was surprising to me honestly that by default sockets are created in non blocking mode. More over, it's looks like it's not some built-in default behaviour, it is explicitly made non-blocking in places like this:

SDL_net/src/SDL_net.c

Line 958 in 2e6b797

if (MakeSocketNonblocking(server->handle) < 0) {

So I would like to have the set/get functions for that at least, and to have sockets blocking by default at most.