On Sat, Jul 25, 2015 at 5:24 AM, Matthias Wessendorf <matzew(a)apache.org>
sorry for the late response ;-)
On Thu, Jul 23, 2015 at 10:51 PM, Summers Pittman <supittma(a)redhat.com>
> So good news,
> Topic support for GCM is trivial to implement. In fact after 20 minutes
> I have most of the work done in the Android library. The behavior of
> topics matches the behavior of categories. I would like to propose some
> 1) Changing categories/topics currently requires the application to
> unregister and reregister on UPS. I would like to add a subscribe and
> unsubscibe method to the pushRegistrar interface which will subscribe and
> unsubscribe the device from topics.
Ok, makes sense. Actually I like the idea. Should this be done on the
other SDKs too? If so... does it make sense to change the RESTful endpoint
to? e.g. do a PUT to update the device metadata?
So strictly speaking we don't need to have GCM 3 Android register its
categories with UPS. Google can handle those.
How are we handling compatibility? Would it be weird if 1.2 of UPS requires
ADroid push 3.0?
I recall we kinda had this talk before. See:
> 2) All Message listeners receive messages from all topics the device is
> subscribed to. I would like to extend registrar manager to be able to
> attach messages handlers per topic as well as globally.
Due to the nature of the Android layer around GCM 3, this is specific to
Android only, right ?
I don't know enough about iOS, sorry :(
+1 on this. Same reasoning like Erik Jan here :)
> This are both simple, easy changes which shouldn't be a lot of work and
> will really improve the push experience in Agdroid 3.0.
bring it on :)
> aerogear-dev mailing list
aerogear-dev mailing list