Very well. What I meant is that in general, the vocabulary used in Microsoft Windows and its various C++-oriented libraries is generally not the one that is used in the more standard, cross-platformish interfaces. As such, it is silly to assume that e.g. google would produce anything pertinent with the search "asynchronous sockets in C", since first, "C" and "C++" map to the same search keyword and second, "asynchronous" is not the correct expression for dealing with sockets in the first place (for various, generally UNIX-specific reasons which are too long to go into here).

To be constructive, I would suggest that >>1 instead google for information on non-blocking sockets, or more generally non-blocking I/O in POSIX. The reason for the latter is that sockets are just a special case of file descriptor, the mechanism by which endpoints of serial communication (among other things) are implemented in UNIX, and as such the techniques used for non-blocking I/O generally apply to sockets just like they do to e.g. named pipes or TTY devices.