Return-Path: Delivered-To: apmail-jakarta-httpcomponents-dev-archive@www.apache.org Received: (qmail 23124 invoked from network); 4 Sep 2007 09:07:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Sep 2007 09:07:56 -0000 Received: (qmail 22757 invoked by uid 500); 4 Sep 2007 09:07:50 -0000 Delivered-To: apmail-jakarta-httpcomponents-dev-archive@jakarta.apache.org Received: (qmail 22733 invoked by uid 500); 4 Sep 2007 09:07:50 -0000 Mailing-List: contact httpcomponents-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list httpcomponents-dev@jakarta.apache.org Received: (qmail 22724 invoked by uid 99); 4 Sep 2007 09:07:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 02:07:50 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [213.46.255.22] (HELO viefep28-int.chello.at) (213.46.255.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 09:09:00 +0000 Received: from [192.168.0.63] (really [212.71.105.68]) by viefep28-int.chello.at (InterMail vM.7.08.02.02 201-2186-121-104-20070414) with ESMTP id <20070904090725.LFYC18690.viefep28-int.chello.at@[192.168.0.63]> for ; Tue, 4 Sep 2007 11:07:25 +0200 Subject: Re: Regarding Async server in NIO Example From: Oleg Kalnichevski To: HttpComponents Project In-Reply-To: <46DD19F9.2020409@odi.ch> References: <632145970709032223n5683b2a4v805416cc8a695173@mail.gmail.com> <1188894775.5564.3.camel@okhost> <46DD19F9.2020409@odi.ch> Content-Type: text/plain; charset=ISO-8859-1 Date: Tue, 04 Sep 2007 11:07:24 +0200 Message-Id: <1188896844.5564.10.camel@okhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org On Tue, 2007-09-04 at 10:40 +0200, Ortwin Gl�ck wrote: > > Oleg Kalnichevski wrote: > > What do you mean by the 'backlog limit for the server socket'? Maximum > > content buffer length? > > I think he refers to the number of not-yet-accepted TCP connections (SYN > received, but not ACKed). See second parameter of ServerSocket(int, > int). Basically connections must be accepted one by one. But in the > meantime the connections keep queuing up until the backlog limit is > reached. From that point on new connections will get a RST packet instead. > > Odi > I see. NIO does not seem to expose this option because the server socket get instantiated behind the scene by the ServerSocketChannel. So the system default should apply. Oleg > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org