I was investigating on HttpCore4 and erroneously was convinced that
HttpCore is the evolution of HttpClient3, but , Roland and others
promptly corrected this in previous message Right now I have one
project to begin and was evaluating the roadmap and relationship of
HttpCore and HttpClient Project will have to use HttpClient in the
middle of the july and I was curious:
1) what will be the form of the new HttpClient (API aspect)
2) Can I have some guidance when contributing the code (naming,
structure, testing) ?
3) what are the pieces that HttpClient4 lack ?
4) when will we have first alpha ?
5) will be relatively easy to migrate the HttpClient v3 code to v4 ?
Thanks
To unsubscribe, e-mail: httpclient-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: httpclient-dev-help (AT) jakarta (DOT) apache.org

Mon, 2006-06-12 at 10:45 +0200, Stojce Dimski wrote:
I was investigating on HttpCore4 and erroneously was convinced that
HttpCore is the evolution of HttpClient3, but , Roland and others
promptly corrected this in previous message

Right now I have one
project to begin and was evaluating the roadmap and relationship of
HttpCore and HttpClient Project will have to use HttpClient in the
middle of the july and I was curious:

1) what will be the form of the new HttpClient (API aspect)

HttpCore is intended to provide only the very basic transport services
sufficient allowing to send and receive HTTP messages. It is meant to be
content and service agnostic

HttpClient will remain what it is now. HttpClient 4 will be a direct
equivalent of HttpClient in terms of functionality, albeit having a
different API and a more modular architecture

HttpClient 4 will be based on HttpCore and will provide additional
services on top of it:
* Cookie and HTTP state management
* HTTP authentication
* Automatic redirect handling
* Connection management / pooling

2) Can I have some guidance when contributing the code (naming,
structure, testing) ?

We do not have any formal guidelines. We do love test cases, though. Any
code contribution accompanied by test cases will have a much higher
likelihood of being accepted

3) what are the pieces that HttpClient4 lack ?

I am in the process of rewriting the cookie management code. All other
bits are still missing.

4) when will we have first alpha ?

The first alpha is unlikely to be released this year.

5) will be relatively easy to migrate the HttpClient v3 code to v4 ?

Probably not. After all HttpClient 4.0 is meant to be a complete rewrite
of the entire code line. However, 30 to 40% performance gain and much
smaller memory footprint should be a strong incentive for migration.

Thanks

There are two categories of applications whose developers should
seriously consider using HttpCore instead of HttpClient 3.x at this
point:
* server side services and proxies
* web spiders

HttpClient 3.x API is simply not well suited for these types of
application. All other users should stick to HttpClient 3.x for the time
being. It may have an ugly API but it is well tested and is _very_
stable

Hope this makes things somewhat clearer

To unsubscribe, e-mail: httpclient-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: httpclient-dev-help (AT) jakarta (DOT) apache.org

To unsubscribe, e-mail: httpclient-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: httpclient-dev-help (AT) jakarta (DOT) apache.org