Re: [Aerogear-users] categories have been hijacked

On Mon, Apr 18, 2016 at 10:30 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Coming back to this, after a loooooooooooooong, looooooong time... > > > ---------- Forwarded message ---------- > From: Summers Pittman <supittma(a)redhat.com&gt; > Date: Tue, Aug 11, 2015 at 2:31 PM > Subject: Re: [Aerogear-users] categories have been hijacked > To: aerogear-users(a)lists.jboss.org > > > > > On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford <kelvin(a)qantel.com&gt; > wrote: > >> Hi Summers, >> >> GCM topic messages go to all devices registered for the topic. Topic >> notifications cannot be restricted to an alias or list of aliases. >> >> The way it worked before, and still works on ios, you can send a command >> to UPS with an "alias" name AND a "categories" name and it will only go to >> devices that have registered using that "alias" name AND that "categories" >> name. UPS finds which devices meet the selection criteria and push >> notification requests are sent for those devices. >> >> Requests with aliases and categories can target specific users in a >> group. >> >> With real "categories" you can segment users into groups, so every >> device can be assigned a category, and sub-groups can be defined by using >> more than one category per device. This is useful for geographic or >> organizational targeting. >> >> I have no problem with GCM topics. Just make it a new feature. Give me >> back my categories. >> > > So the goal isn't to replace or hijack categories with topics. The goal > is to leverage Google's API fully and transparently to the UPS user so that > we make fewer calls and provide a better experience. You have some great > use cases that haven't been brought up. Keep in mind that the PRs open > right now are a "first draft" of the technology. > > > > NOTE: Between Google IO 2015 and now, April 2016, there was a change on > topics: No more limitations of subscribed devices! Before it was limited to > 1 million. > > Now, this also means options :-) We could just auto register each android > device to one topic (e.g. /topics/VARIANT_ID), *IF* there is no category > provided! > I think you mean always register a device to a variant specific topic.

That way we can send all Android GCM users a message with one push message from the push server.

> > Regarding the concerns, to 'alias' or any other criteria, my > understanding is that, for now, we just use GCM topic only if nothing else, > than the category is provided to the RESTful Sender API. > > However, we could extend our Device Group feature, and kinda group all > devices to a users group, and have the category play in there too. E.g. > have some groups like: > * matthias_football > * matthias_music > but the sending here, would be a message to a device group, not a category > > -Matthias > > > > > Feel free to join in on the discussion about topics on aerogear-dev. > It is really important we do this right and I think you can help with that. > > Summers > > >> - Kelvin >> >> >> >> --------------------------------------------------------------------------------------- >> From: aerogear-users-bounces(a)lists.jboss.org [mailto: >> aerogear-users-bounces(a)lists.jboss.org] On Behalf Of Summers Pittman >> Sent: Monday, August 10, 2015 6:12 PM >> To: aerogear-users(a)lists.jboss.org >> Subject: Re: [Aerogear-users] categories have been hijacked >> >> >> > >> >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford <kelvin(a)qantel.com&gt; >> wrote: >> >Setting "categories" in the push payload was working for android and >> ios in cordova push plugin 1.1.1. >> > >> >For version 2.0.2 "categories" only works for ios. >> > >> >It looks like "categories" is being hijacked in android for a GCM >> feature called "topics". >> > >> >I liked "categories". I was using it. Now it's gone. GCM topics is >> not a drop-in replacement. It's not the same thing. >> >> What do categories do that topics do not do? >> >> >New features should get new names and new commands. >> > >> >- Kelvin >> >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > _______________________________________________ Aerogear-users mailing list Aerogear-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users