Impact of using select with blocking and non-blocking sockets

c network-programming nonblocking select-function
DaTaBomB picture DaTaBomB · Feb 24, 2013 · Viewed 7.2k times · Source

How will my program differ in behavior if I use non-blocking sockets with a select() call as opposed to using blocking sockets with a select() call?

Answer

Some programmer dude picture Some programmer dude · Feb 24, 2013

The select polling will not behave differently, only the receive/send functionality will differ between blocking/non-blocking sockets.

Related questions

What's the difference between async and nonblocking in unix socket?

I'm seeing such code in nginx: if(fcntl(ngx_processes[s].channel[0], F_SETFL, fcntl(s, F_GETFL) | O_NONBLOCK) == -1) { ... if (ioctl(ngx_processes[s].channel[0], FIOASYNC, &on) == -1) { ... Anyone can tell me what's the difference between fcntl(…

Read More
C: socket connection timeout

I have a simple program to check if a port is open, but I want to shorten the timeout length on the socket connection because the default is far too long. I'm not sure how to do this though. Here's …

Read More
socket connect() vs bind()

Both connect() and bind() system calls 'associate' the socket file descriptor to an address (typically an ip/port combination). Their prototypes are like:- int connect(int sockfd, const struct sockaddr *addr, socklen_t addrlen); and int bind(int sockfd, …

Read More