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

Karel Piwko kpiwko at redhat.com
Tue Sep 17 11:46:10 EDT 2013


On Tue, 17 Sep 2013 17:23:25 +0200
Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Callback do not make to much sense for the java implementation IMO (maybe
> for the Node implementation it makes more sense) but for the Java
> Implementation of the Sender we could discuss on :

I think callback makes sense even if its synchronous, especially if Sender API
is synchronous as well.

> - returning the http status code rather than returning void

How useful is returning a status response without response body? 

> 
> - have a better exception handling and introduce a Sender specific Exception

+1

> 
> 
> 
> On Tue, Sep 17, 2013 at 5:17 PM, Karel Piwko <kpiwko at redhat.com> 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?
> >
> > Thanks,
> >
> > Karel
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >



More information about the aerogear-dev mailing list