This content originally appeared on DEV Community and was authored by Vivek Yadav
Introduction:
In the realm of network programming with C, mastering the intricacies of socket operations is paramount. Among the fundamental concepts in this domain are blocking and non-blocking sockets, which significantly influence the behavior and performance of networked applications. In this comprehensive guide, we delve into the nuanced differences between blocking and non-blocking sockets, explore their respective advantages and disadvantages, and provide practical examples to illustrate their usage in C programming.
Blocking Sockets:
Blocking sockets, also known as synchronous sockets, adhere to a straightforward paradigm: I/O operations halt the execution of the program until they are completed. When you read from or write to a blocking socket, your program will pause until data is available to be read or the write operation finishes. This synchronous behavior simplifies the flow of the program, making it intuitive for developers, especially those new to network programming.
Key characteristics of blocking sockets include:
Blocking Behavior: I/O operations block the program's execution until they conclude.
Synchronous Operation: Operations are performed in a synchronous manner, meaning the program waits until each operation finishes before proceeding.
Simplicity: Blocking sockets offer simplicity and ease of understanding, making them an attractive choice for beginners in network programming.
However, the simplicity of blocking sockets comes at a cost. Consider a scenario where a blocking socket is used to communicate with multiple clients simultaneously. If one client's operation takes an unexpectedly long time to complete, it may block the entire program, potentially causing delays in serving other clients.
To illustrate, let's consider a basic example of using blocking sockets in a TCP client-server application:
Server (TCP Server)
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <arpa/inet.h>
#define PORT 8080
#define MAX_PENDING_CONNECTIONS 5
#define BUFFER_SIZE 1024
int main() {
int server_fd, new_socket;
struct sockaddr_in address;
int addrlen = sizeof(address);
char buffer[BUFFER_SIZE] = {0};
const char *message = "Hello from server";
// Create socket file descriptor
if ((server_fd = socket(AF_INET, SOCK_STREAM, 0)) == 0) {
perror("socket failed");
exit(EXIT_FAILURE);
}
// Set server address parameters
address.sin_family = AF_INET;
address.sin_addr.s_addr = INADDR_ANY;
address.sin_port = htons(PORT);
// Bind the socket to the specified port
if (bind(server_fd, (struct sockaddr *)&address, sizeof(address)) < 0) {
perror("bind failed");
exit(EXIT_FAILURE);
}
// Listen for incoming connections
if (listen(server_fd, MAX_PENDING_CONNECTIONS) < 0) {
perror("listen failed");
exit(EXIT_FAILURE);
}
printf("Server listening on port %d...\n", PORT);
// Accept incoming connection
if ((new_socket = accept(server_fd, (struct sockaddr *)&address, (socklen_t*)&addrlen)) < 0) {
perror("accept failed");
exit(EXIT_FAILURE);
}
// Read client message
read(new_socket, buffer, BUFFER_SIZE);
printf("Client message: %s\n", buffer);
// Send response to client
send(new_socket, message, strlen(message), 0);
printf("Response sent to client.\n");
// Close sockets
close(new_socket);
close(server_fd);
return 0;
}
Client (TCP Client)
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <arpa/inet.h>
#define PORT 8080
#define SERVER_ADDRESS "127.0.0.1"
#define BUFFER_SIZE 1024
int main() {
int sock = 0;
struct sockaddr_in serv_addr;
char buffer[BUFFER_SIZE] = {0};
const char *message = "Hello from client";
// Create socket file descriptor
if ((sock = socket(AF_INET, SOCK_STREAM, 0)) < 0) {
perror("socket creation failed");
exit(EXIT_FAILURE);
}
// Set server address parameters
serv_addr.sin_family = AF_INET;
serv_addr.sin_port = htons(PORT);
// Convert IPv4 and IPv6 addresses from text to binary form
if (inet_pton(AF_INET, SERVER_ADDRESS, &serv_addr.sin_addr) <= 0) {
perror("invalid address / address not supported");
exit(EXIT_FAILURE);
}
// Connect to server
if (connect(sock, (struct sockaddr *)&serv_addr, sizeof(serv_addr)) < 0) {
perror("connection failed");
exit(EXIT_FAILURE);
}
// Send message to server
send(sock, message, strlen(message), 0);
printf("Message sent to server.\n");
// Read response from server
read(sock, buffer, BUFFER_SIZE);
printf("Server response: %s\n", buffer);
// Close socket
close(sock);
return 0;
}
Non-blocking Sockets:
In contrast to blocking sockets, non-blocking sockets operate asynchronously. When an I/O operation is initiated on a non-blocking socket, the program continues its execution immediately, regardless of whether the operation succeeds or not. This asynchronous behavior allows the program to perform other tasks while waiting for I/O operations to complete, enhancing overall efficiency and responsiveness.
Key characteristics of non-blocking sockets include:
Non-blocking Behavior: I/O operations return immediately, even if they cannot be completed immediately.
Asynchronous Operation: Operations are performed asynchronously, enabling the program to continue executing without waiting for each operation to finish.
Increased Complexity: Non-blocking sockets introduce additional complexity into the program logic, as it needs to handle situations where operations may not complete immediately.
While non-blocking sockets offer improved responsiveness and better resource utilization, they require careful handling of asynchronous events. Developers must implement mechanisms to manage the asynchronous nature of non-blocking sockets effectively, such as employing event loops or using multiplexing techniques like select() or poll().
Let's examine a practical example demonstrating the use of non-blocking sockets in a TCP client-server application:
Server (Non-blocking TCP Server)
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <arpa/inet.h>
#include <fcntl.h>
#define PORT 8080
#define MAX_PENDING_CONNECTIONS 5
#define BUFFER_SIZE 1024
int main() {
int server_fd, new_socket;
struct sockaddr_in address;
int addrlen = sizeof(address);
char buffer[BUFFER_SIZE] = {0};
const char *message = "Hello from server";
// Create socket file descriptor
if ((server_fd = socket(AF_INET, SOCK_STREAM, 0)) == 0) {
perror("socket failed");
exit(EXIT_FAILURE);
}
// Set server address parameters
address.sin_family = AF_INET;
address.sin_addr.s_addr = INADDR_ANY;
address.sin_port = htons(PORT);
// Bind the socket to the specified port
if (bind(server_fd, (struct sockaddr *)&address, sizeof(address)) < 0) {
perror("bind failed");
exit(EXIT_FAILURE);
}
// Set the server socket to non-blocking mode
if (fcntl(server_fd, F_SETFL, O_NONBLOCK) < 0) {
perror("fcntl failed");
exit(EXIT_FAILURE);
}
// Listen for incoming connections
if (listen(server_fd, MAX_PENDING_CONNECTIONS) < 0) {
perror("listen failed");
exit(EXIT_FAILURE);
}
printf("Server listening on port %d...\n", PORT);
while (1) {
fd_set readfds;
int max_sd, activity;
// Clear the socket set
FD_ZERO(&readfds);
// Add server socket to the set
FD_SET(server_fd, &readfds);
max_sd = server_fd;
// Wait for activity on any socket
activity = select(max_sd + 1, &readfds, NULL, NULL, NULL);
if (activity < 0) {
perror("select error");
exit(EXIT_FAILURE);
}
// If server socket has activity, it's a new connection
if (FD_ISSET(server_fd, &readfds)) {
if ((new_socket = accept(server_fd, (struct sockaddr *)&address, (socklen_t*)&addrlen)) < 0) {
perror("accept failed");
exit(EXIT_FAILURE);
}
printf("New connection, socket fd is %d\n", new_socket);
// Send message to client
if (send(new_socket, message, strlen(message), 0) != strlen(message)) {
perror("send failed");
}
close(new_socket); // Close the connection
}
}
return 0;
}
Client (Non-blocking TCP Client)
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <arpa/inet.h>
#include <fcntl.h>
#define PORT 8080
#define SERVER_ADDRESS "127.0.0.1"
#define BUFFER_SIZE 1024
int main() {
int sock = 0;
struct sockaddr_in serv_addr;
char buffer[BUFFER_SIZE] = {0};
const char *message = "Hello from client";
// Create socket file descriptor
if ((sock = socket(AF_INET, SOCK_STREAM, 0)) < 0) {
perror("socket creation failed");
exit(EXIT_FAILURE);
}
// Set server address parameters
serv_addr.sin_family = AF_INET;
serv_addr.sin_port = htons(PORT);
// Convert IPv4 and IPv6 addresses from text to binary form
if (inet_pton(AF_INET, SERVER_ADDRESS, &serv_addr.sin_addr) <= 0) {
perror("invalid address / address not supported");
exit(EXIT_FAILURE);
}
// Set the socket to non-blocking mode
if (fcntl(sock, F_SETFL, O_NONBLOCK) < 0) {
perror("fcntl failed");
exit(EXIT_FAILURE);
}
// Connect to server
if (connect(sock, (struct sockaddr *)&serv_addr, sizeof(serv_addr)) < 0) {
// Non-blocking connect will return immediately
// Check errno to distinguish between connection in progress and connection failed
if (errno != EINPROGRESS) {
perror("connection failed");
exit(EXIT_FAILURE);
}
}
// Wait for connection to complete
sleep(1);
// Send message to server
send(sock, message, strlen(message), 0);
printf("Message sent to server.\n");
// Read response from server
read(sock, buffer, BUFFER_SIZE);
printf("Server response: %s\n", buffer);
// Close socket
close(sock);
return 0;
}
Conclusion:
In conclusion, understanding the distinctions between blocking and non-blocking sockets is essential for proficient network programming in C. While blocking sockets offer simplicity and straightforward operation, non-blocking sockets provide greater flexibility and efficiency by enabling asynchronous I/O operations. When selecting the appropriate socket mode for your application, consider the specific requirements, scalability, and performance constraints. With a solid grasp of blocking and non-blocking socket concepts, developers can architect robust and responsive networked applications tailored to their unique needs.
This content originally appeared on DEV Community and was authored by Vivek Yadav
Vivek Yadav | Sciencx (2024-07-08T01:11:02+00:00) Understanding Blocking and Non-blocking Sockets in C Programming: A Comprehensive Guide. Retrieved from https://www.scien.cx/2024/07/08/understanding-blocking-and-non-blocking-sockets-in-c-programming-a-comprehensive-guide/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.