To use or not to use Netty

[Ersin Er]

Netty is a completely async framework at both server and client sides. The
http client library is an advanced example which handles conversational
logic as it needs to map async responses to async requests.

Ersin from Galaxy S2
On Sep 1, 2011 2:50 PM, "Ngoc Dao" <ngocdaothanh at gmail.com> wrote:
> How about this?
> https://github.com/sonatype/async-http-client
>
> It is based on Netty.
>
> Ngoc
>
>
> On Thu, Sep 1, 2011 at 8:22 PM, Shardul Bhatt <shardul.bhatt at gmail.com>
wrote:
>> Hi Ngoc,
>>
>> Thanks for your reply
>>
>> I am more interested in knowing if I can use Netty to send 'Asynchronous
>> Requests'
>>
>>  /
>>        Response response1 = send(Request1);
>>        Response response2 = send(Request2);
>>        Response response3 = send(Request3);
>>  /
>>
>> It should be such that the application doe snot wait for Request1 to
return
>> a response and initiate send(Request2) and then initiate send(Request3).
>>
>> I would want to avoid using Multithreading, or rather would want to do it
>> using a Framework.
>>
>> Regards,
>> Shardul.
>>
>> --
>> View this message in context:
http://netty-forums-and-mailing-lists.685743.n2.nabble.com/To-use-or-not-to-use-Netty-tp6749001p6749693.html
>> Sent from the Netty User Group mailing list archive at Nabble.com.
>> _______________________________________________
>> netty-users mailing list
>> netty-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/netty-users
>>
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20110904/e09cbf1a/attachment.html