ICEmobile
  1. ICEmobile
  2. MOBI-345

Android must support new Google Cloud Messaging for Cloud Push

          Details

          • Type: New Feature New Feature
          • Status: Resolved
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.1 Final
          • Fix Version/s: 1.2 Beta
          • Component/s: Containers
          • Labels:
            None
          • Environment:
            Android Container and ICEpush-ee

            Description


            C2DM has been deprecated and replaced with Google Cloud Messaging (GCM). The Android container and ICEpush EE infrastructure need to support GCM. While legacy support for C2DM is desirable, it is not necessary to support both from a single server-side application.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Steve Maryka added a comment - - edited

              Investigation into the migration path from C2DM to GCM indicates that client code can remain the same, with the only required change being the sender id.
              The server-side is a bit different. The authentication process is gone, and now only a server key is required to send. The existing C2DM data format is preserved, so only the message header needs to change. A new notification provider for GCM is warranted.
              Configuration of the notification provider requires the server key that matches the GCM sender code. Project credentials are created/configured through googleapis. The GCM notification provider configured into the application either using a Java system property:
              -Dcom.icesoft.icepush.gcmlogin="Server key for your GCM project"
              or in the web.xml using
              <context-param>
              <param-name>gcm.authKey</param-name>
              <param-value>Server key for your GCM project</param-value>
              </context-param>

              Show
              Steve Maryka added a comment - - edited Investigation into the migration path from C2DM to GCM indicates that client code can remain the same, with the only required change being the sender id. The server-side is a bit different. The authentication process is gone, and now only a server key is required to send. The existing C2DM data format is preserved, so only the message header needs to change. A new notification provider for GCM is warranted. Configuration of the notification provider requires the server key that matches the GCM sender code. Project credentials are created/configured through googleapis. The GCM notification provider configured into the application either using a Java system property: -Dcom.icesoft.icepush.gcmlogin="Server key for your GCM project" or in the web.xml using <context-param> <param-name>gcm.authKey</param-name> <param-value>Server key for your GCM project</param-value> </context-param>
              Hide
              Permalink
              Steve Maryka added a comment - - edited

              rev:32568 improved logging. Jira being resolved.

              Show
              Steve Maryka added a comment - - edited rev:32568 improved logging. Jira being resolved.

                People

                • Assignee:
                  Steve Maryka
                  Reporter:
                  Steve Maryka
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: