<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 6, 2015 at 10:14 AM, Sebastien Blanc <span dir="ltr">&lt;<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <span dir="ltr">&lt;<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Y&#39;all,<div><br></div><div>Since I now have a GCM Topic PR up I figure it is time to revisit beefing up categories a bit.</div><div><br></div><div>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</div></div></blockquote><div><br></div></span><div>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 <a href="https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80</a> </div><span class=""><div>  </div></span></div></div></div></blockquote><div><br></div><div>Oooo.  So just spamming register is an option. Thanks!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>We also discussed adding the ability to &quot;route&quot; 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&#39;t use GCM topics.  It will also require updates on the client code.</div></div></blockquote></span><div>Can you elaborate a bit on that or point me to previous  discussions ?  </div></div></div></div></blockquote><div>I was thinking of edewit&#39;s comment: </div><div>  <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html</a> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><div dir="ltr"><div><br></div><div>As an aside there is also GCM support on iOS, but it is much more complicated to set up.</div></div>
<br></span>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div></div>
<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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div></div>