You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Techie India <it...@gmail.com> on 2007/09/03 07:26:15 UTC
Regarding HTTP Core Features..
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.
Re: Regarding HTTP Core Features..
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Mon, 2007-09-03 at 16:29 +0530, Techie India wrote:
> So what you will say when you compare HTTP Core to Coyote HTTP connector in
> terms of features.
>
> Thanks.
>
Big fat disclaimer: I have only worked with Coyote 5.5.x. All I am about
to say may no longer apply to version 6.x
Coyote HTTP was never developed with extensibility and flexibility in
mind. It is a very old codebase, which grew quite messy over time. It
has been optimized for one thing and one thing only - performance, at
the expense of everything else. Moreover it was optimized to perform on
older JVMs. Lots of those optimization techniques are no longer even
relevant. There is simply no way to customize many aspects of Coyote. It
is a monolithic, cryptic body of code crammed into just a handful of
classes. If Coyote works for you, great, but there are things you want
done differently, you are out of luck. Last time I checked Coyote does
not provide any support for the HTTP state management or authentication.
Those aspects are provided by Catalina.
Bottom line: HttpCore and Coyote are approximately equal feature-wise,
but HttpCore is infinitely more modular and customizable.
Hope this helps
Oleg
>
> On 9/3/07, Oleg Kalnichevski <ol...@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 <ol...@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
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
Re: Regarding HTTP Core Features..
Posted by Techie India <it...@gmail.com>.
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 <ol...@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 <ol...@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
>
>
Re: Regarding HTTP Core Features..
Posted by Oleg Kalnichevski <ol...@apache.org>.
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 <ol...@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.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
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
Re: Regarding HTTP Core Features..
Posted by Techie India <it...@gmail.com>.
i am mostly looking at the features which tomcat supports for the HTTP.....
1)UrlEncoding
2)Authentication.
3)Cookies.
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.
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.
Thanks
On 9/3/07, Oleg Kalnichevski <ol...@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.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
>
>
Re: Regarding HTTP Core Features..
Posted by Oleg Kalnichevski <ol...@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