<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 30, 2017 at 9:32 AM, Oleh Mackiv <span dir="ltr"><<a href="mailto:omatskiv@redhat.com" target="_blank">omatskiv@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi, <br></div>I think this very much depends on what is the actual limit for number of topics.<br><br>Consider this use case, that would max out topics very quickly: <br>- register alias for each user<br>- if user has multiple devices, all his devices will have same alias<br></div>- if you want to notify some user, you just send notification to his alias and UPS will distribute it to all devices that this user has registere<br></div><br><div>We even suggest this in docs[1]:<br>"<code class="m_3763877550171893055gmail-highlighter-rouge">alias</code>: A list of one or more <em>identifiers</em> (such as <code class="m_3763877550171893055gmail-highlighter-rouge">email</code> or <code class="m_3763877550171893055gmail-highlighter-rouge">username</code>) to send messages to <em>ALL</em> devices of the user(s)" </div><div><br><br>P.S: Do you know how much topics you can actually register before you hit the "messaging/too-many-topics" error ?<br></div></div></blockquote><div><br></div><div>I think it isn't set. Google has not been very open with the limits on the topic mechanism. (At one point there was a one million subscriber limit). Regardless, I think we can probably beef up UPS to fall back to standard sending mechanisms if we get errors, it can eve be part of our value add.</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><br><br>[1] <a href="https://aerogear.org/docs/unifiedpush/push-message-format/#query-component" target="_blank">https://aerogear.org/docs/<wbr>unifiedpush/push-message-<wbr>format/#query-component</a><br><div><br><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Tue, May 30, 2017 at 2:43 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><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><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><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's on the app instance (see [1]), so our APP Developers need to make sure they don't go crazy w/ a gazillion of categories ;-) </div><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_3763877550171893055HOEnZb"><font color="#888888"><br></font></span></div><span class="m_3763877550171893055HOEnZb"><font color="#888888"><div><br></div><div>-- <br><div class="m_3763877550171893055m_2617726808533415466gmail_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></div></div><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_3763877550171893055gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div>Oleg Matskiv<br></div>Associate Quality Engineer<br></div><div>Red Hat Mobile Application Platform<br></div><a href="mailto:omatskiv@redhat.com" target="_blank">omatskiv@redhat.com</a><br></div></div></div></div>
</font></span></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></div></div>