> > (Unix at least; Win32 connect is a mess for non-blocking/timed-out > > sockets... it looks to me that we wait forever; I could be confused > > though :) ) > > > > concerns? > > > > old behavior on Unix: > > > > if timeout is set on socket before apr_connect() and connect takes a > > while (normal for TCP), apr_connect() returns EINPROGRESS and app must > > handle any timeout > > > > new behavior on Unix: > > > > if timeout is set on socket before apr_connect(), app will see > > APR_ETIMEUP if it takes longer than the timeout
+1 (apr_wait_for_io_or_timeout() might want a better name if it's going public, but that's just a nit) --Cliff -------------------------------------------------------------- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA
