On Tue, Aug 18, 2009 at 12:53 AM, Paul Sandoz<Paul.Sandoz_at_sun.com> wrote:
> On Aug 17, 2009, at 8:13 PM, Morten wrote:
>
>> HttpClient 4.0 (GA) has now finally been released. Would it be possible to
>> release a new stable build of jersey client soon that uses HttpClient 4.0
>> internally?
>>
>
> What would be the reason to upgrade?
AFAIK, 4.0 is a significant improvement over 3.0; and specifically
cleaning up most of API.
Which unfortunately means that:
>
> Is 4.0 backwards compatible with 3.x?
it's not backwards compatible at all. :)
(which is part of why it took a while to do it etc, and slows down adoption)
But I think new API is in different package(s), so it may be possible
for 3.x and 4.x backends to peacefully co-exist at least?
> If it is not backwards compatible then it will require more work to
> integrate and will require 3.x and 4.0 be supported. I currently do not have
> the time to do this, but would encourage others to contribute if they want
> 4.0 support, as it should be possible to plug in such an implementation to
> the client API.
It would be great to add such support; I understand resource
limitations of course.
But it's hard to get benefits of httpclient upgrade without support
from frameworks... chicken and egg problem pretty much.
-+ Tatu +-