<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 17, 2013 at 2:15 PM, Daniel Passos <span dir="ltr"><<a href="mailto:daniel@passos.me" target="_blank">daniel@passos.me</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><span lang="en"><span>I was thinking</span> <span>about it</span><span>.</span> <span>That</span> <span>would be the responsibility</span> <span>of the library</span> <span>or application</span><span>?<br>
</span></span></div></div></blockquote><div><br></div><div>I think the lib should give an error msg, and do the log (+retry).</div><div><br></div><div>The app should be able, I think, to responsed to that error msg</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><span lang="en"><span>
<br></span></span></div><span lang="en"><span>Btw, any thoughts?<br></span></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 27, 2013 at 12:59 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So with GCM and Android, Google may decide to update the devices token.<br>
The device will receive a Intent saying that the token has changed and<br>
it needs to eventually update the remote server's data before the token<br>
expires.<br>
<br>
Right now the application checks the device id on startup and<br>
reregisters if there is a change. If the user doesn't interact with the<br>
applicaiton for a long period of time and the device token changes he<br>
will eventually stop receiving messages.<br>
<br>
Ideally, I would think that handling this as soon as the intent comes in<br>
would be great. However, how should failures to reregister be handled?<br>
My easy answer is Log and retry with exponential backoff (and maybe send<br>
a error message).<br>
<br>
WDYT?<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>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>