<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 15, 2013 at 1:59 PM, TadeasKriz <span dir="ltr"><<a href="mailto:tkriz@redhat.com" target="_blank">tkriz@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div>I've created the JIRA subtask:</div>
<div><br></div><div><a href="https://issues.jboss.org/browse/AGDROID-62" target="_blank">https://issues.jboss.org/browse/AGDROID-62</a></div><div><br></div><div>You said some push networks recommend not to unregister from device. Well, I was more thinking about it like the device will send information to the unified push server and the server will then remove the device from the list of available tokens.</div>
</div></blockquote><div><br></div><div><br></div><div>Well - Apple is pretty strict about "not following" best practices.</div><div><br></div><div>In iOS there is a notification centre. There the user will disable "notification" per app (and users know that). And that's exactly why Apple has a Feedback Service to query for "invalid" tokens.</div>
<div><br></div><div>Regardless if we all love things or not, I guess for the iOS SDK we will not see a "unregister" hook (for those above reasons). </div><div><br></div><div>Kinda sucks if a developer's app got's rejected because AeroGear-iOS, and its developers :-)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div> Also the device would unregister from the push network if it should (I think it's valid way with GCM, don't know about others).</div>
<div><br></div><div>From the API side, I think it might be added as a method of Registrar. So there would be Registrar#register and Registrar#unregister. What do you think?</div></div></blockquote><div><br></div><div>yes, I guess that's what the JIRA ticket is for, right ? </div>
<div><br></div><div><br></div><div>The UnifiedPush Server does have this API endpoint already:</div><div><a href="https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-push-rest/DeviceRegistration.asciidoc#unregister-of-a-device-http-delete">https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-push-rest/DeviceRegistration.asciidoc#unregister-of-a-device-http-delete</a><br>
</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><div class="h5"><div><br></div><br><div><div>On Jul 15, 2013, at 12:57 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite">
it is opional, since some push networks recommend not performing "in app unregister" themselves. (eg APNs). There are (APNs)hooks to query for invalid tokens (aka feedback service).<div><br></div><div>For Android SDK, can u file JIRA sub task of AGDROID-35 ?</div>
<div><br></div><div>Thanks,</div><div>Matthias</div><div><br></div><div>PS: there is no real harm, if payload to push network contains "outdated" tokens.</div><div><br></div><div><br></div><div><span></span><br>
<br>On Monday, July 15, 2013, TadeasKriz wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hey,<br>
<br>
I'm now trying the unified push with Android and I've noticed, that there is no way (or I didn't find it?) to unregister the device. Example real usage: in application settings there might be a checkbox to disable notifications, so the user probably won't like receiving push messages which would then be discarded by the device (it'd be a waste of his data package). It seems to me like it wasn't left out on purpose, but rather forgotten to be added. Any thoughts on this?<br>
<br>
Thanks<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a>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>-- <br>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><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></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>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>