android - How many registration IDs per device and and user does Google Cloud Messaging (GCM) issue? -
i'm implementing gcm handler on server. google issue new registration id per device or per user? know issue new id per app version , user, extend each device user has app installed on?
ultimately, ask because want know how should store registration id user's app sends me server-side.
right have implemented such sent id user's registration id, unsure if incorrect way model how gcm handles registration ids. i'm leaning towards being incorrect , i'd have keep record of many ids based on criteria.
any input appreciated.
basically, gcm issues new registration id per device app installed. answer question, 1 registration id per device.
gcm not know own users, implement logic of how sift through messages intended user x , y, if both of them use same device.
here's docs:
a registration id isn't associated particular logged in user. if unregister , re-register, gcm may return same id or different id—there's no guarantee either way. make sure messages go intended user:
- your app server can maintain mapping between current user , registration id.
- the app can check ensure messages receives match logged in user.
the whole "matching" concept in last bullet meant sifting through.
Comments
Post a Comment