You are not logged in.
Pages: 1
int socket_fd, result;
fd_set readset;
...
/* Socket has been created and connected to the other party */
...
/* Call select() */
do {
FD_ZERO(&readset);
FD_SET(socket_fd, &readset);
result = select(socket_fd + 1, &readset, NULL, NULL, NULL);
} while (result == -1 && errno == EINTR);
if (result > 0) {
if (FD_ISSET(socket_fd, &readset)) {
/* The socket_fd has data available to be read */
result = recv(socket_fd, some_buffer, some_length, 0);
if (result == 0) {
/* This means the other side closed the socket */
close(socket_fd);
}
else {
/* I leave this part to your own implementation */
}
}
}
else if (result < 0) {
/* An error ocurred, just print it to stdout */
printf("Error on select(): %s\", strerror(errno));
}Offline
Overall only two things that jump out at me... I've been busy so only had a chance for a quick glance at the code but...
In the first part of the explanation... might want to explicitly state that its sockets you want to monitor for readability...
The other is the mixing of C and C++ style comments... I do this myself to "seperate" function call comments and those comments about the internal operation of a function but if someone tries to compile with a "pure" C compiler, it won't understand the // bit...
Of course, anyone who can program in C at all and read a program should understand both of those but... you KNOW what sorta questions we get from the newbies on the site ;-)
Michael
"The only difference between me and a madman is that I'm not mad."
Salvador Dali (1904-1989)
Offline
Pages: 1