Yes of course.
But as I told in a previous post onsucess, onerror is a standard way to
"organize" things, only that.
People need to know they are walking on known territory, dealing as far as
possible with standard concepts. That's a small thing, not important at
all, but we must in general pay attention to that kind of issues.
On Wed, Feb 26, 2014 at 7:20 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
On Wednesday, February 26, 2014, Miguel Lemos <miguel21op(a)gmail.com>
wrote:
> onSucess = the device has managed to register on the service. It's a one
> time info, but priceless if we are still struggling to figure out how to
> make the whole thing work. For the end user, no that has no use.
>
If dev registration is not successful: onError is called; IMO that's
almost same: dev does know: whoops something went wrong
> About the simplification: 130000% agree :)
>
> About the sound: useless, if we want to make it ring, don't need the
> push notification API to do it. The badge (I even don't know what those
> values - 1, 3, 7... - mean, not yet...)
>
badge, as explained in our message format spec is apple keyword:
http://aerogear.org/docs/specs/aerogear-push-messages/
--
Sent from Gmail Mobile
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev