[aerogear-dev] Java Sender API - fire&forget - adding callback methods?

Sebastien Blanc scm.blanc at gmail.com
Tue Oct 8 09:14:28 EDT 2013


FYI Karel has created a Jira for this
https://issues.jboss.org/browse/AGPUSH-373



On Tue, Sep 24, 2013 at 11:43 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> On Thu, 19 Sep 2013 10:13:52 -0400
> Summers Pittman <supittma at redhat.com> wrote:
>
> > On 09/18/2013 09:37 AM, Karel Piwko wrote:
> > > On Wed, 18 Sep 2013 09:31:36 -0400
> > > Summers Pittman <supittma at redhat.com> wrote:
> > >
> > >> On 09/17/2013 11:17 AM, Karel Piwko wrote:
> > >>> Hi,
> > >>>
> > >>> I went once again through
> > >>> http://lists.jboss.org/pipermail/aerogear-dev/2013-June/002901.html-
> > >>> which says that Sender API should be fire&forget. It feels more like
> > >>> "maybe fire"&forget, for instance it does not say that your
> credentials
> > >>> were wrong
> > >>> - or it says, you need parse logs to get that information.
> > >>>
> > >>> If I think about Android, iOS, JS solutions to communicate with
> > >>> UnifiedPush we provide - Pipes - they always provide a callback to be
> > >>> executed on success/failure. Could we add callback to Sender API? Or
> > >>> should not Aerogear rather have something like Pipes abstraction for
> Java
> > >>> developers instead of pretty dumb Sender API?
> > >>>
> > >>> Thoughts?
> > >> In a bit of crazy land perhaps the client could keep a web socket or
> BSD
> > >> Socket open to the server which would let it get callbacks about
> things
> > >> that happen further down the tree.
> > > Isn't this land called vert.x?
> > Maybe I misunderstood.  I thought it was wanting to get information from
> > the push server about the status of messages being sent not the response
> > of the commands to the push server itself.
>
> I was speaking about the latter.
>
> > >
> > >>> Thanks,
> > >>>
> > >>> Karel
> > >>> _______________________________________________
> > >>> aerogear-dev mailing list
> > >>> aerogear-dev at lists.jboss.org
> > >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> _______________________________________________
> > >> aerogear-dev mailing list
> > >> aerogear-dev at lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> 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/20131008/526f1d15/attachment.html 


More information about the aerogear-dev mailing list