<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/17/2013 08:15 AM, Daniel Passos
wrote:<br>
</div>
<blockquote
cite="mid:CAKjsGbtkStEb4wyFecxH-97mU3FANP8abFhHkSixpSt4pTngVQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><span id="result_box" class="" lang="en"><span class="">I
was thinking</span> <span class="">about it</span><span>.</span>
<span class="">That</span> <span class="">would be the
responsibility</span> <span class="">of the library</span>
<span class="">or application</span><span>?<br>
<br>
</span></span></div>
<span id="result_box" class="" lang="en"><span>Btw, any
thoughts?<br>
</span></span></div>
</blockquote>
Well I marked it as won't fix because this factoid doesn't appear in
any of Google's docs any more. I am going to assume since they
don't mention it anywhere anymore that it isn't necessary anymore.<br>
<blockquote
cite="mid:CAKjsGbtkStEb4wyFecxH-97mU3FANP8abFhHkSixpSt4pTngVQ@mail.gmail.com"
type="cite">
<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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aerogear-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</body>
</html>