How has Google implemented their push notification feature? Does it work through polling done by a service running in the background or in a different way?
Below are the methods you can try. The first solution is probably the best. Try others if the first one doesn’t work. Senior developers aren’t just copying/pasting – they read the methods carefully & apply them wisely to each case.
From what I’ve heard during an Android developers conference in Israel:
There is simply a TCP socket waiting in accept mode on a cloud Google server. The TCP connection had been initiated by the Google Play application. That’s why Google Play must be installed on the device for making Google Cloud Messaging (GCM) (formerly Android Cloud to Device Messaging Service – C2DM) work.
When this TCP client socket receives some message, the message contains information such as the package name of the application it should be addressed to, and of course – the data itself. This data is parsed and packed into an intent that is broadcast and eventually received by the application.
The TCP socket stays open even when the device’s radio state turns into “idle” mode. Applications don’t have to be running to receive the intents.
More information at http://developer.android.com/google/gcm/gcm.html
Android keeps one active connection to Google’s servers, but it doesn’t use much power or data, because no traffic is sent along it until something sends a Google Cloud Messaging (GCM) message to an app on your phone. There’s only one connection on the phone, used by all apps: installing a new app that uses GCM doesn’t add any extra load.
The first step in GCM is that a third-party server (such as an email server) sends a request to Google’s GCM server. This server then sends the message to your device, through that open connection. The Android system looks at the message to determine which app it’s for, and starts that app. The app must have registered with Android to use GCM, and it must have the relevant permission. When the app starts, it might create a notification straight away with the data from the message. GCM messages are very limited in size, so the app might instead open a normal connection to the third-party server to get more information (for example, downloading the headers of new emails).
The advantage of using push notifications is that apps don’t have to run at regular intervals to check for new data, saving both power and data. The advantage of having a centralized mechanism like GCM is that the device only needs one open network connection and the Android GCM system is the only thing that needs to keep running, rather than each app having to stay running in the background to keep its own network connection to its own server.
Took this from : Source
Also see here.
You can implement the push notification on android yourself with a long polling tcp connection.
But that would involve maintaining an extra socket => battery drain.
Or you can open a connection at regular intervals using the Alarm Manager.
Google probably opens one socket for all the C2DM push notifications, hence its more battery efficient.
As of April 10, 2018, Google has deprecated GCM. The GCM server and client APIs are deprecated and will be removed as soon as April 11, 2019. Migrate GCM apps to Firebase Cloud Messaging (FCM), which inherits the reliable and scalable GCM infrastructure, plus many new features.
Yes, you’re right. Google had a service (GTalk Service) and this service asked Google servers in some periods of time.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0