<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 5, 2015 at 9:26 AM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.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">Hello Sebi,<div><br></div><div><br></div><div>I've done an initial work on aerogear-ios-push [swift branch], adding a new parameter when doing the registration to pass the ag-push-id. See:</div><div>
<p><span><a href="https://github.com/aerogear/aerogear-ios-push/compare/aerogear:master...corinnekrych:AGPUSH-1232.analytics.push.notification?expand=1" target="_blank">https://github.com/aerogear/aerogear-ios-push/compare/aerogear:master...corinnekrych:AGPUSH-1232.analytics.push.notification?expand=1</a></span></p><p>This client could be tested with HelloWorld. See:</p><p>
</p><p>
</p><p><span><a href="https://github.com/jboss-mobile/unified-push-helloworld/compare/jboss-mobile:swift...corinnekrych:AGPUSH-1232.analytics.push.notification?expand=1" target="_blank">https://github.com/jboss-mobile/unified-push-helloworld/compare/jboss-mobile:swift...corinnekrych:AGPUSH-1232.analytics.push.notification?expand=1</a></span></p><p><span>What is not covered is the background app coming to foreground through a push notification. If you look at HelloWorld:</span></p><p>
</p><p><span><a href="https://github.com/jboss-mobile/unified-push-helloworld/blob/f7d0a7e093327f9a84041910c4c2892280c88ffb/ios-swift/HelloWorldSwift/AppDelegate.swift#L152" target="_blank">https://github.com/jboss-mobile/unified-push-helloworld/blob/f7d0a7e093327f9a84041910c4c2892280c88ffb/ios-swift/HelloWorldSwift/AppDelegate.swift#L152</a></span></p><p>In iOS, when we go from background to foreground we don't go through registration API. The iOS push lib doesn't store locally (as opposed to windows sdk for ex) the device information. So i can't really make another call to registration API. What i'd suggest is to have a separate endpoint for metrics instead of having it coupled with registration endpoint. wdyt?</p></div></div></blockquote><div><br></div><div>Ok, if that's needed, it has to be done! Thanks for the feedback and research here. But before we change, let's see how it behaves on Android</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><p>++<span class="HOEnZb"><font color="#888888"><br></font></span></p></div><span class="HOEnZb"><font color="#888888"><div>Corinne</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 4 May 2015 at 19:07, Sébastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.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="auto"><div>Hi Corinne !</div><div>We want to collect for both situations you described :)<br><br>Envoyé de mon iPhone</div><div><div><div><br>Le 4 mai 2015 à 17:53, Corinne Krych <<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>> a écrit :<br><br></div><blockquote type="cite"><div><div dir="ltr">Hello Sebi,<div><br><div>After giving it a closer look, I've got a question for you: do we want to collect metrics only when an app is opened via push notification or do we also want to collect metrics when an app is brought to foreground by a push notification?</div></div><div><br></div><div>++</div><div>Corinne</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 4 May 2015 at 10:21, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.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">Yeap<div>on it.</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On 30 April 2015 at 15:43, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</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><div dir="ltr">Hi,<div><br></div><div>The Advanced Analytics task[1] has a new PR[2] that has been rebased on the latest master and got a lot of polishing.</div><div><br></div><div>Could the Client Tech Leads take a look at it [3] and review ? The only "breaking" change is the rename of the header's name that identifies a Push Notification, it's called now "aerogear-push-id" </div><div><br></div><div>Seb</div><div><br></div><div><br></div><div><br></div><div>[1] <a href="https://issues.jboss.org/browse/AGPUSH-971" target="_blank">https://issues.jboss.org/browse/AGPUSH-971</a></div><div>[2] <a href="https://github.com/aerogear/aerogear-unifiedpush-server/pull/540" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-server/pull/540</a></div><div>[3] Subtasks of <a href="https://issues.jboss.org/browse/AGPUSH-971" target="_blank">https://issues.jboss.org/browse/AGPUSH-971</a></div><div><br></div><div><br></div></div>
<br></div></div>_______________________________________________<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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>aerogear-dev mailing list</span><br><span><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></span></div></blockquote></div></div></div><br>_______________________________________________<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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>
</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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</div></div>