[aerogear-dev] [Java Sender API] future of AsyncHttpClient

[Sebastien Blanc]

On Wed, Jul 10, 2013 at 9:52 AM, Matthias Wessendorf <matzew at apache.org>wrote:

>
>
>
> On Wed, Jul 10, 2013 at 9:41 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
>
>> Hi Folks !
>> As you know the current Java Sender API comes today with 2 different
>> implementations :
>>
>> - Resteasy client (used by default)
>> - AsyncHttpClient
>>
>> I discussed a bit with Matzew and we agreed that we should probably
>> remove the AsyncHttpClient implementation and just keep the resteasy
>> client, wdyt ?
>>
>
>
> yep, I'd prefer one client (based on RestEasy). Also that means we don't
> need all the JavaSender, DefaultSender etc...
>
+1

>
> We just have one client, and need to name it "reasonably".
>
Yea how should we name it ?

>
> I'd also argue that we should worry that the client can be injected, using
> CDI. Makes sense when being used on JavaEE backends
>
isn't that the responsability of the backend app using the sender or is
there anything to do on the sender side ? (in the latest case a jira would
be cool)


>
>
>
>>
>> Seb
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130710/8e083a9b/attachment-0001.html