Android C2DM : Duplicate message to the same device and App?

Not sure if this is the best approach, but there's a relevant thread over at the android-c2dm group, where the poster offers one technique.

Not sure if this is the best approach, but there's a relevant thread over at the android-c2dm group, where the poster offers one technique: I am sending registration id in the message, so I can check it against the stored registration id on the device. If it's not the same, discard it and notify the service that registration Id is no longer in use Downside is sending registration Id takes up some space in already limited message size. But works perfectly in my case since my original message is no more than a few chars long.

Great technique! It seems very smart – Matroska yesterday.

Yup, I've run into the same issue and in my opinion it's a big oversight in the Android C2DM implementation. IOS handles this much better in that an app can only ever receive notifications for one and only one device token (equivalent of the c2dm registration id) The workaround I use is to send the last 10 characters of the registration id as part of the c2dm payload and then in my onMessage method I do the following check: if (!regId. EndsWith(bundle.

GetString("regsuffix"))) return null.

Another solution could be to provide your server with a unique identifier for the device. In that case you can just update the registrationID for that UUID when the device tries to register after re-installation.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.