Android Cloud to Device Messaging
 Overview of the C2DM Service architecture. | |
| Developer(s) | |
|---|---|
| Target platform(s) | Android, Chrome |
| Programming language(s) | Java |
| Status | Discontinued |
| License | Open-source |
| Website | developers |
Android Cloud to Device Messaging (commonly referred to as Cloud to Device Messaging), or C2DM, is a deprecated mobile service developed by Google. It enables developers to send data from servers to Android applications and Chrome extensions. C2DM originally launched in 2010 and was available beginning with version 2.2 of Android.[1] Google announced official deprecation of the C2DM service on June 27, 2012. In August 2013, Google unveiled the Google Cloud Messaging service aimed at replacing the now-deprecated C2DM platform, citing improvements to authentication and delivery, new API endpoints and messaging parameters, and the removal of API rate limits and maximum message sizes.[2] The C2DM is no longer available for newly released Android applications and is scheduled to be discontinued for existing applications and shut down on October 20, 2015.[3]
Technical details
The C2DM service consists of sub-services and interfaces necessary with maintaining security and reliability. When an application registers for C2DM messages and data, it receives a C2DM Registration ID from the service. This identifier is unique to the application on the device, and is used to identify the device that the data or message request is intended for. This identifier is typically sent by the client application to a server owned by the developer or creator for tracking and statistical purposes. Upon sending a data or push request, the server sends an authentication request and the C2DM Registration ID of the device to the C2DM authentication service, which responds with an authentication token upon success. The third party server then takes both identifiers and submits the final data request to be enqueued and sent to the device. When the device receives the information from the C2DM, the request is removed from the C2DM queue.[4]
Migration to the Google Cloud Messaging service
Shortly after announcing the Google Cloud Messaging service, Google published documentation to guide application developers with migrating from the C2DM and onto the GCM.[5] Migrating to the GCM requires SDK and code changes, as well as a release of an application update to the publish repository (such as Google Play) for downloading and updating. The C2DM and the GCM are not interoperable between each other; you cannot send data requests using for one service by using another. The migration can also changes to the third party server of developers.[5]
References
- ^ Vogel, Lars (September 12, 2011). "Android Cloud to Device Messaging (C2DM) - Tutorial". Retrieved October 15, 2015.
- ^ Rubio, Daniel (August 12, 2012). "Google Cloud Messaging for Android (GCM) Unveiled, to Replace C2DM Framework". Retrieved October 15, 2015.
- ^ "Cloud to Device Messaging (Deprecated)". Google. Retrieved October 15, 2015.
- ^ Meier, Reto (March 22, 2012). Professional Android 4 Application Development. 2. Indianapolis, Indiana: John Wiley and Sons, Inc. ISBN 978-1118102275. Retrieved October 15, 2015.
{{cite book}}: Unknown parameter|publicationplace=ignored (|publication-place=suggested) (help) - ^ a b "Migration from C2DM". Google. Retrieved October 15, 2015.