push notification - Limit collapse_key count in android GCM. Part 2 -

push notification - Limit collapse_key count in android GCM. Part 2 -

i've asked collapse key limit , right reply here @ianhanniballake. now, want precise something. limit on gcm collapse_keys on per app level. mean app level? example, there 2 apps installed on 2 corresponds devices, i.e.

device1->appinstance1->reg1 device2->appinstance2->reg2

whether each app's instance can have 4 collapse keys maximum or 4 collapse keys on app instances? link between gcm registration id , 4 collapse keys, 4 collapse keys per 1 registration id or 4 collapse keys per registrtion ids (per users of app)? in our app have user session entity, can live 2 mounth, can utilize session id collapse key or collapse key must constant string? help me please!

the 4 collapse key maximum 4 per device, means 4 per app instance (and since each app instance has different registration id, means 4 per 1 registration id).

gcm allows maximum of 4 different collapse keys used gcm server per device given time. in other words, gcm server can simultaneously store 4 different send-to-sync messages, each different collapse key.

(source)

as using session id collapse key, there nil stopping doing that, there no need. since messages collapsed same collapse key , same registration id, can utilize same collapse key in app instances. i'm assuming create server code simpler.

android push-notification google-cloud-messaging