Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Received-SPF: unknown ipv4:213.46.255.15/27 (nike.apache.org: encountered
 unrecognized mechanism during SPF processing of domain of odi@odi.ch)
Message-ID: <4B69496B.5090600@odi.ch>
Date: Wed, 03 Feb 2010 11:01:15 +0100
From: =?UTF-8?B?T3J0d2luIEdsw7xjaw==?= <odi@odi.ch>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: HttpComponents Project <dev@hc.apache.org>
Subject: Re: Controlling "acceptance" of connections
References: <4B68F7F0.2030101@apache.org>
 <4B693140.50601@odi.ch>	 <4B693C75.3020001@apache.org>
 <1265191113.7256.29.camel@ubuntu>
In-Reply-To: <1265191113.7256.29.camel@ubuntu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


On 03.02.2010 10:58, Oleg Kalnichevski wrote:
> I think NIO should work quite similarly. A selectable channel can be
> marked as OP_ACCEPT ready, but that does not mean the connection
> listener must accept that connection or accept it immediately.  

In theory yes. But you get the ACCEPT ready *once* only. So if you ignore it,
you forget that a channel was ready and you can end up never accepting it. So
not registering for OP_ACCEPT in the first place when you can't handle new
sockets is a must.

Odi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org