[aerogear-dev] AGDROID-80 and unified Push

[Matthias Wessendorf]

On Tue, Sep 17, 2013 at 2:15 PM, Daniel Passos <daniel at passos.me> wrote:

> I was thinking about it. That would be the responsibility of the library or
> application?
>

I think the lib should give an error msg, and do the log (+retry).

The app should be able, I think, to responsed to that error msg


>
> 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
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130917/78f74420/attachment.html