<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 18, 2013 at 3:31 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 09/17/2013 11:17 AM, Karel Piwko wrote:<br>
> Hi,<br>
><br>
> I went once again through<br>
> <a href="http://lists.jboss.org/pipermail/aerogear-dev/2013-June/002901.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2013-June/002901.html</a> - which<br>
> says that Sender API should be fire&forget. It feels more like "maybe<br>
> fire"&forget, for instance it does not say that your credentials were wrong - or<br>
> it says, you need parse logs to get that information.<br>
><br>
> If I think about Android, iOS, JS solutions to communicate with<br>
> UnifiedPush we provide - Pipes - they always provide a callback to be executed<br>
> on success/failure. Could we add callback to Sender API? Or should not Aerogear<br>
> rather have something like Pipes abstraction for Java developers instead of<br>
> pretty dumb Sender API?<br>
><br>
> Thoughts?<br>
</div>In a bit of crazy land perhaps the client could keep a web socket or BSD<br>
Socket open to the server which would let it get callbacks about things<br>
that happen further down the tree.<br></blockquote><div><br></div><div>-1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">><br>
> Thanks,<br>
><br>
> Karel<br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>