Contact Information:

Product Inquiry:

Cloud Push

What It Does

Cloud Push delivers server-generated, real-time notifications to mobile devices, alerting the user about something of relevance. With ICEfaces applications, Cloud Push is activated automatically for any client that is not actively engaged with the application, so you can always get important information to all your users, active or not. There are two main aspects of Cloud Push, aligning with the client/server nature of the protocol.

User Notification occurs at the client. A cloud push message is received by the mobile device, interpreted, and presented to the user in some fashion. Various types of device-resident alerts, including status indicators, dialogs, ring tones, or vibration can be used to get the users attention. The application is reactivated when a notification is acknowledged, allowing the user to take appropriate actions.

Notification Push occurs at the server. ICEfaces’s Ajax Push mechanism automatically monitors the state of all clients, and determines when they go idle. For idle clients, any subsequent push requests can optionally use an alternate cloud-based transport to send the notification. When a client becomes active again, Ajax Push will revert to the HTTP-based mechanism, push page updates in the standard way.

How To Use It

Building applications with Cloud Push it is simple. The existing Ajax Push mechanism automatically switches to Cloud Push for inactive clients. Simply add an optional cloud push message to your exiting Ajax Push calls and you're done. ICEfaces handles the rest.

A variety of alternate transports are supported with Cloud Push, including generic and platform-specific connectors. Generic connectors rely on existing protocols and device support to deliver alerts. Supported connectors include:

Platform-specific connectors rely on platform-specific push mechanisms on the server, and the ICEfaces Device Containers to receive and process the Cloud Push messages on the client. The following platform-specific connectors are supported.

How It Works

ICEfaces’s Ajax Push mechanism (ICEpush) detects when clients to the application go inactive, and can use an alternate Cloud Push connector to pass notifications to the device. The user notification mechanism of the device will alert the user, who can then reactivate the application and react to the state change. The Cloud Push architecture is illustrated below, and depicts the sequence of events involved in a push.

Cloud Push Architecture Diagram
  1. Client passes cloud push credentials to server, so that server can use device-specific cloud push connector to deliver notifications
  2. Ajax Push mechanism detects that client device goes inactive
  3. Some state change occurs in the application that results in an Ajax Push occurring
  4. The alternate cloud connector is used to send a notification to the inactive device
  5. User notification is produced on the device

Learn More