users@jersey.java.net

[Jersey] Re: AsyncHttpClient + Jersey

From: jfarcand <jfarcand.oss_at_gmail.com>
Date: Thu, 27 Jan 2011 10:06:06 -0500

Salut,

FYI, I was waiting for the contribution before doing more works...I know
the team that did it use it and were supposed to contribute it
back...seems it haven't worked. So I may soon take another look and
implement it myself, as we want to use it @ Sonatype.

A+

-- Jeanfrancois

On 11-01-27 9:09 AM, Pavel Bucek wrote:
> yes, there is a difference and it is like you wrote - Jersey Client
> async support still uses HttpURLConnection; it spawns a new thread which
> is used to execute actual request. I'm not sure how AsyncHttpClient
> works yet, but I'd guess they have their own thread pool which allows
> requests and responses being handled each by different thread..
>
> Pavel
>
>
> On 01/27/2011 01:28 PM, Cem Koc wrote:
>>
>> Hello,
>>
>> Thanks for information.
>>
>> I would like to ask something else also. As far as I know that Jersey has
>> async features. Is there a big difference regarding threading model
>> when you
>> compared with AsyncHttpClient? Is Jersey creating a new thread for
>> each new
>> request?
>>
>> Thanks
>
>