<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 30, 2017 at 3:33 PM, Daniel Passos <span dir="ltr">&lt;<a href="mailto:dpassos@redhat.com" target="_blank">dpassos@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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, May 30, 2017 at 9:43 AM, Matthias Wessendorf <span dir="ltr">&lt;<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>on FCM related push, we do, in our client SDK, automatically subscribe a client to an annoymous topic, matching our immutable variant ID.</div><div><br></div><div>If users are specifying categories, we do map those into topics as well.</div><div><br></div><div>This is the related code in our Android SDK:</div><div><a href="https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/fcm/AeroGearFCMPushRegistrar.java#L188-L193" target="_blank">https://github.com/aerogear/ae<wbr>rogear-android-push/blob/maste<wbr>r/aerogear-android-push/src/<wbr>main/java/org/jboss/aerogear/<wbr>android/unifiedpush/fcm/<wbr>AeroGearFCMPushRegistrar.java#<wbr>L188-L193</a></div><div><br></div><div>How do people feel about doing that for the alias as well ? </div></div></blockquote><div><br></div></span><div>I really like that idea.<br></div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>In the past we did not do it, since topics used to be a more restricted resource. Remember, the first notion of topics (GCM v3, at that time) were even limiting the number of max. subscribers?</div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>However, that changed, and I think it would be nice if we just use the topics for each alias of the app as well. This would speed up the time to deliver the push request to the FCM backend, since the UPS would no longer need to look up the device, a push, regardless how many devices, means one small HTTP to Google, per alias (aka topic)</div><div><br></div><div>Any thoughts ? </div><div><br></div><div>NOTE: There is a general limit of topic abuse, but that&#39;s on the app instance (see [1]), so our APP Developers need to make sure they don&#39;t go crazy w/ a gazillion of categories ;-) </div></div></blockquote></span><div><br><div>Just a heads up about topics limit =&gt; 
<a href="https://stackoverflow.com/questions/38171259/maximum-number-of-topics-a-device-can-subscribe-to-in-fcm" target="_blank">https://stackoverflow.com/<wbr>questions/38171259/maximum-<wbr>number-of-topics-a-device-can-<wbr>subscribe-to-in-fcm</a></div></div></div></div></div></blockquote><div><br></div><div>Right, it&#39;s per device, not for per server-key </div><div><br></div><div>Alias is usually one per device - Categories, which we are already do via topics, do definitely have more room here:</div><div>music, sports, beer, burgers, linux, jboss, and so on ;-) </div><div><br></div><div><br></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"><div><div><br></div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=""><div dir="ltr"><div><br></div><div>-Matthias</div><div><br></div><div><br></div><div>[1] <a href="https://firebase.google.com/docs/cloud-messaging/admin/errors" target="_blank">https://firebase.google.com/do<wbr>cs/cloud-messaging/admin/error<wbr>s</a><span class="m_-7259948012440974448gmail-HOEnZb"><font color="#888888"><br></font></span></div><span class="m_-7259948012440974448gmail-HOEnZb"><font color="#888888"><div><br></div><div>-- <br><div class="m_-7259948012440974448gmail-m_792286141960129957gmail_signature"><div dir="ltr"><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.word<wbr>press.com/</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div></div></div>
</div></font></span></div>
<br></span><span class="">______________________________<wbr>_________________<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/mailma<wbr>n/listinfo/aerogear-dev</a><br></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div class="m_-7259948012440974448gmail_signature"><div dir="ltr">-- Passos<br></div></div>
</font></span></div></div>
<br>______________________________<wbr>_________________<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/<wbr>mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div></div></div>
</div></div>