android - Google cloud messaging Limit -

i know exists similar questions on site, confused because http , xmpp have difference limit:

this page differences between http , xmpp.

first limit [xmpp & http]: up 4kb of data

second limit is:

http: you can send out message 1000 users @ time. (ref)

xmpp: for each sender id, gcm allows 1000 connections in parallel. (ref)

you can send out message 1000 users @ time. if have more users you'll have send message multiple times server different users each time (ref)

third limit is:

http: couldn't found limit in android developer:

there limit on how many messages can stored without collapsing. limit 100. if limit reached, stored messages discarded. when device online, receives special message indicating limit reached. application can handle situation properly, typically requesting full sync. (ref)

xmpp:

every message sent ccs receives either ack or nack response. messages haven't received 1 of these responses considered pending. if pending message count reaches 100, app server should stop sending new messages , wait ccs acknowledge of existing pending messages (ref)

my questions:

1.in second limit, if use http method , have 2000 users, should send message twice, every time 1000 users?, can it?

2.xmpp can not support multicast messaging, can use topic multicast in xmpp?

3. any limit on broadcast messaging topics? (except ref)

4.in third limit, if send message 300 users, , one hundred top users offline, recieve message or notification when come , online? (note: use broadcast http , loop xmpp)

5. do limit effect in topic way ?

6. do exists difference in third limit between http , xmpp?

7.exists other limit in http or xmpp?

1. yes can that. while using http may have batch size of 1000(recipients).

2. yes. topic messages pubsub method , if clients registered given topic, can sent push notification of them 1 request.

3. no limitation. once there 1 million subscriber limit per app on topic messaging, doesn't exist anymore.

4. you confused third limit:

   • the first 1 (http) single client, not of them. if send more 100 messages single client while offline, when gets online again, none of them deliver.
   • the second 1 (xmpp) of queue , happens in server side. means have send no messages gcm if there exists more 100 unacked messages there.

   so have no problem considering offline users, gcm handle deliver message of them, when come online.

5. no.

6. i explained in 4.

7. i don't remember more.