Geek asks and answers

Reliability of an Android upstream app?

I want to use ccs upstreaming messages to send messages from my application to the ccs application server. I wrote code for the ccs application server and it is connected to the gcm server. Sometimes sent messages are delivered to the server quickly, as instantly, but in most cases they do not work. All my posts contain ttl as 0 in the gcm.send () function. If I try to send more messages using ttl 0 gcm, you will get the message "Too many messages." Is there a way to find out if the sent message was sent using the upstream method to the ccs server (any application for the client application even before the message reaches our xmpp application server)? As a client, gcm deals with ttl of different messages. (let's say the first 10 posts don't have ttl,and the 11th message has a ttl of 5 and after that 2 messages with ttl 0). How will these messages be delivered to the ccs server, in what order, if all messages are sent continuously in less than 5 seconds (for example, all at a time)?

Thanks SM

+3
source share
1 answer

As in downstream messages, an upstream message with ttl = 0 is sent immediately or never, depending on the network status and the connection between the GCM client device and the CCS server.

I describe here a related problem with some previous versions of Android.

Short answer: upstream messaging is reliable in KK, not in previous versions.

0
source

More articles:


All Articles