When I compare the win32 implementation of apr_socket_recv() against other implementations, one thing seems to jump out. On all other platforms the apr_socket_recv() function calls apr_wait_for_io_or_timeout() if recv() returns and EWOULDBLOCK and there is a timeout specified in the sock structure. In the Win32 implementation any timeout value in the sock structure is simply ignored. Is there a reason for this or is it an oversight?
Brad Nicholes Senior Software Engineer Novell, Inc., the leading provider of Net business solutions http://www.novell.com
