hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Techie India" <ittechie.in...@gmail.com>
Subject Re: Regarding HTTP Core Features..
Date Mon, 03 Sep 2007 10:59:41 GMT
So what you will say when you compare HTTP Core to Coyote HTTP connector in
terms of features.

Thanks.


On 9/3/07, Oleg Kalnichevski <olegk@apache.org> wrote:
>
> On Mon, 2007-09-03 at 14:37 +0530, Techie India wrote:
> > i am mostly looking at the features which tomcat supports for the
> HTTP.....
> > 1)UrlEncoding
> > 2)Authentication.
> > 3)Cookies.
> >
>
> All of these features are out of the HttpCore scope. There are no plans
> to provide them in HttpCore. We might look into possibility of building
> an embeddable HTTP server at some point of time but currently we do not
> even have enough committers to work on HttpCore and HttpClient.
>
>
> > Do you have any comparable data of HTTPCore API and Tomcat Http.
> > means what are the features for HTTP  which are not supported by HTTP
> Core
> > in comparision to Tomcat.
> >
>
> We do not want to be seen as a competitor to Tomcat or any other servlet
> engine. HttpCore is more comparable to Coyote HTTP connector than
> Catalina container.
>
> > Actually we are using the Embedded tomcat in our application for giving
> HTTP
> > Support, But we are facing some performance issue there so we want to
> > replace that with HTTP Core based Server.
> >
>
> As much I would like to see HttpCore used more widely I think you may be
> better served by Jetty, if what you essentially want is a different
> servlet engine.
>
> Hope this helps
>
> Oleg
>
>
> > Thanks
> >
> >
> > On 9/3/07, Oleg Kalnichevski <olegk@apache.org> wrote:
> > >
> > > 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.Iwant
> > > 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
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> httpcomponents-dev-help@jakarta.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message