apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@attglobal.net>
Subject Re: win32/apr_socket_recv() vs others...
Date Mon, 27 Jan 2003 23:47:44 GMT
Brad Nicholes wrote:

>     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?

I see that Mr. Rowe has answered differently already, but I thought the 
answer was this:

When the timeout is set (and stored in apr_socket_t), a Win32 socket 
option is set so that the Windows kernel handles the timeout without APR 
having to use multiple syscalls to perform the same function.

View raw message