[aerogear-dev] AGDROID-80 and unified Push

[Summers Pittman]

On 09/17/2013 08:15 AM, Daniel Passos wrote:
> I was thinking about it. That would be the responsibility of the 
> library or application?
>
> Btw, any thoughts?
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.
>
>
> On Tue, Aug 27, 2013 at 12:59 PM, Summers Pittman <supittma at redhat.com 
> <mailto:supittma at redhat.com>> wrote:
>
>     So with GCM and Android, Google may decide to update the devices
>     token.
>     The device will receive a Intent saying that the token has changed and
>     it needs to eventually update the remote server's data before the
>     token
>     expires.
>
>     Right now the application checks the device id on startup and
>     reregisters if there is a change.  If the user doesn't interact
>     with the
>     applicaiton for a long period of time and the device token changes he
>     will eventually stop receiving messages.
>
>     Ideally, I would think that handling this as soon as the intent
>     comes in
>     would be great.  However, how should failures to reregister be
>     handled?
>     My easy answer is Log and retry with exponential backoff (and
>     maybe send
>     a error message).
>
>     WDYT?
>     _______________________________________________
>     aerogear-dev mailing list
>     aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130918/30d91fc5/attachment.html