Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 51515 invoked by uid 500); 10 Jul 2001 15:08:41 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 51074 invoked from network); 10 Jul 2001 15:08:34 -0000 X-Authentication-Warning: cobra.cs.Virginia.EDU: jcw5q owned process doing -bs Date: Tue, 10 Jul 2001 11:08:33 -0400 (EDT) From: Cliff Woolley X-X-Sender: To: APR Development List Subject: Re: [PATCH] make socket timeouts work reasonably for connect() In-Reply-To: <004001c10947$bd78e7b0$f1431b09@sashimi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > > (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 cliffwoolley@yahoo.com Charlottesville, VA