[aerogear-dev] AGDROID-80 and unified Push
Daniel Passos
daniel at passos.me
Tue Sep 17 08:15:22 EDT 2013
I was thinking about it. That would be the responsibility of the library or
application?
Btw, any thoughts?
On Tue, Aug 27, 2013 at 12:59 PM, Summers Pittman <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
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130917/7d0f720d/attachment.html
More information about the aerogear-dev
mailing list