Return-Path: Delivered-To: apmail-jakarta-httpcomponents-dev-archive@www.apache.org Received: (qmail 42462 invoked from network); 3 Sep 2007 08:52:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Sep 2007 08:52:03 -0000 Received: (qmail 8807 invoked by uid 500); 3 Sep 2007 08:51:58 -0000 Delivered-To: apmail-jakarta-httpcomponents-dev-archive@jakarta.apache.org Received: (qmail 8782 invoked by uid 500); 3 Sep 2007 08:51:57 -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 8773 invoked by uid 99); 3 Sep 2007 08:51:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2007 01:51:57 -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; Mon, 03 Sep 2007 08:53:04 +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 <20070903085131.EYQU18690.viefep28-int.chello.at@[192.168.0.63]> for ; Mon, 3 Sep 2007 10:51:31 +0200 Subject: Re: Regarding HTTP Core Features.. From: Oleg Kalnichevski To: HttpComponents Project In-Reply-To: <632145970709022226j78ef423cicede7340c5fb9655@mail.gmail.com> References: <632145970709022226j78ef423cicede7340c5fb9655@mail.gmail.com> Content-Type: text/plain Date: Mon, 03 Sep 2007 10:51:25 +0200 Message-Id: <1188809485.5685.5.camel@okhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Mon, 2007-09-03 at 10:56 +0530, Techie India wrote: > Hi, > > I recently started looking at the httpCore Api's and the examples.I want to > know what are all the features which HTTP Core Supports on the Server Side. > > Thanks. HttpCore is a set of low level components that implement requirements of the most essential requirements of the HTTP protocol as specified in RFC2616. HttpCore is meant to be content agnostic: it is intended to facilitate transfer of arbitrary content from one end point to another but it is NOT intended to perform content transformation or processing of any kind. HttpCore is both an abstract API and a default implementation of that API. HttpCore Base builds on the classic blocking I/O model and depends on a 1.3 compatible JRE only. HttpCore NIO is based on the non-blocking I/O (NIO) model and requires HttpCore Base and a 1.4 compatible JRE. Both models have their pros and cons. We usually recommend classic I/O for those applications for best performance, while NIO model is more appropriate for use cases where ability to handle thousands of concurrent connections in a resource efficient manner is more important than the raw data throughput. Do you have any specific server-side features / functionality in mind? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org