[aerogear-dev] UPS Categories going forward

[Matthias Wessendorf]

On Thu, Aug 6, 2015 at 4:30 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> +1 on this I think it's very useful to have a specific listener per
> topic/category like I said before ;)
>

agreed


>
> -1 on re-using register, even though that already works, I would like a
> new endpoint to make it's intent more clear also, some clients need to
> store things locally to be able to call register multiple times (iOS and
> windows). But we could do it as an initial version.
>

agreed! We even have a ticket for this new endpoint, that just updates the
metadata:
https://issues.jboss.org/browse/AGPUSH-1399


>
> On Thu, Aug 6, 2015 at 4:23 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>> On Thu, Aug 6, 2015 at 10:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>> Y'all,
>>>>
>>>> Since I now have a GCM Topic PR up I figure it is time to revisit
>>>> beefing up categories a bit.
>>>>
>>>> Before we discussed enhancing the server and client APIs so one could
>>>> subscribe and unsubscribe to topics without unregistering and
>>>> reregistering.  This will require a new endpoint on UPS and new code in all
>>>> the libraries
>>>>
>>>
>>> I agree we need a  PUT /device/metadata (or smt like that) even if today
>>> we support updating of existing installations; if you register an existing
>>> device, it will just update its metadata
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80
>>>
>>>
>>>
>>
>> Oooo.  So just spamming register is an option. Thanks!
>>
>>
>>>
>>>> We also discussed adding the ability to "route" messages to specific
>>>> handlers based on what category the message was sent to.  This will require
>>>> adding a field to all push messages that don't use GCM topics.  It will
>>>> also require updates on the client code.
>>>>
>>> Can you elaborate a bit on that or point me to previous  discussions ?
>>>
>> I was thinking of edewit's comment:
>>
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html
>>
>>
>>>
>>>> As an aside there is also GCM support on iOS, but it is much more
>>>> complicated to set up.
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150811/d2e6f19a/attachment-0001.html