To install click the Add extension button. That's it.

The source code for the WIKI 2 extension is being checked by specialists of the Mozilla Foundation, Google, and Apple. You could also do it yourself at any point in time.

How to transfigure the Wikipedia

Would you like Wikipedia to always look as professional and up-to-date? We have created a browser extension. It will enhance any encyclopedic page you visit with the magic of the WIKI 2 technology.

Try it — you can delete it anytime.

Install in 5 seconds
4,5
Kelly Slayton
Congratulations on this excellent venture… what a great idea!
Alexander Grigorievskiy
I use WIKI 2 every day and almost forgot how the original Wikipedia looks like.
Live Statistics
English Articles
Improved in 24 Hours
Added in 24 Hours
Languages
Recent
Show all languages
What we do. Every page goes through several hundred of perfecting techniques; in live mode. Quite the same Wikipedia. Just better.
Great Wikipedia has got greater.
.
Leo
Newton
Brights
Milds

Android Cloud to Device Messaging

From Wikipedia, the free encyclopedia

Android Cloud to Device Messaging
Overview of the C2DM Service architecture.
Developer(s)Google
Target platform(s)Android, Chrome
Programming language(s)Java
StatusDiscontinued
LicenseOpen-source
Websitedevelopers.google.com/android/c2dm/ Edit this on Wikidata

Android Cloud to Device Messaging (commonly referred to as Cloud to Device Messaging), or C2DM, is a defunct mobile notification service that was developed by Google and replaced by the Google Cloud Messaging service. It enabled 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] On June 27, 2012, Google unveiled the Google Cloud Messaging service aimed at replacing C2DM, citing improvements to authentication and delivery, new API endpoints and messaging parameters, and the removal of API rate limits and maximum message sizes.[2] Google announced official deprecation of the C2DM service in August 2012, and released documentation to assist developers with migrating to the new service. The C2DM service was discontinued for existing applications and completely shut down on October 20, 2015.[3]

YouTube Encyclopedic

  • 1/3
    Views:
    23 674
    2 629
    4 524
  • Mastering C2DM: The Android Cloud to Device Messaging Framework
  • Android Cloud to Device Messaging
  • Migrate from Google Cloud Messaging to Firebase Cloud Messaging - Firecasts

Transcription

Technical details

The C2DM service consisted of sub-services and interfaces necessary with maintaining security and reliability. When an application registered for C2DM messages and data, it received a C2DM Registration ID from the service. This identifier was unique to the application on the device, and was used to identify the device that the data or message request was intended for. This identifier was 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 sent an authentication request and the C2DM Registration ID of the device to the C2DM authentication service, which responded with an authentication token upon success. The third party server then submitted both identifiers within the final data request to be enqueued and sent to the device. When the device received the information from the C2DM, the request was 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 new service.[5] Migrating to the service required SDK and code changes, as well as a release of an application update to the publishing repository (such as Google Play) for downloading and updating. The C2DM and the Google Cloud Messaging service were not interoperable between each other; you could not send data requests using one service to be received and processed on the client app using the other. The migration also required changes to be made on the third party server operated by the developer (depending on the complexity and use case regarding the data sent).[5]

References

  1. ^ Vogel, Lars (September 12, 2011). "Android Cloud to Device Messaging (C2DM) - Tutorial". Retrieved September 4, 2016.
  2. ^ Rubio, Daniel (August 12, 2012). "Google Cloud Messaging for Android (GCM) Unveiled, to Replace C2DM Framework". Retrieved October 15, 2015.
  3. ^ "Cloud to Device Messaging (Deprecated)". Google. Retrieved October 15, 2015.
  4. ^ 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. c2dm registration id.
  5. ^ a b "Migration from C2DM". Google. Archived from the original on September 6, 2015. Retrieved October 15, 2015.

External links

Official website

This page was last edited on 7 December 2023, at 12:17
Basis of this page is in Wikipedia. Text is available under the CC BY-SA 3.0 Unported License. Non-text media are available under their specified licenses. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc. WIKI 2 is an independent company and has no affiliation with Wikimedia Foundation.
Contact WIKI 2
Introduction
Terms of Service
Privacy Policy