Hey thanks for your reply Appreciate it very much! Rendy
On Apr 24, 4:16 pm, EhyehAsherEhyeh <jacobsen.ar...@gmail.com> wrote: > Presumably there is some two-way communication between Google's > servers and the device, so server-side will know whether a device is > available to receive the message and fire off a registration intent. > Bottom line: I would think Google would be capable enough to realize > the issue and handle it, so you can proceed with the assumption that > if the registration id is changed there will be an intent broadcast to > indicate such. > I frame these statements with "Presumably" and "I would think" because > I have been surprised by seemingly broken Android behaviour in the > past, but still, I say you shouldn't worry about this particular > issue. > > On Apr 24, 4:55 am, ndiiie 90 <rnd...@gmail.com> wrote: > > > > > > > > > Hi all, > > > I am interested in implementing C2DM for the push notification feature in > > my application. > > However, when I read the > > docshttps://developers.google.com/android/c2dm/#lifecycle > > It states that: "Note that Google may periodically refresh the registration > > ID, so you should design your application with the understanding that the > > REGISTRATION Intent may be called multiple times. Your application needs to > > be able to respond accordingly" > > > How about if the case is the device has no connection when Google refresh > > the registration ID? Of course the REGISTRATION Intent will not be called. > > Does Google try to refresh again the registration ID? > > If not, how can the device know that the Google refresh the registration ID? > > > Thanks, > > > Rendy -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
