What can the Push Service offer?

Increased efficiency
You can choose where to send content. Using the Push Service, you can send content to:
  • Individual users (unicast)
  • Many users (multicast)
  • All of your users (broadcast)
The Push Initiator sends the content when it's available so that data traffic is generated only when necessary. Additionally, with the Push Plus service level, your push solution can store push requests on a local database on the push server. If the Push Initiator receives a result notification, it can then perform status queries locally.
End-to-end message visibility

With the Push Plus service level, you can receive up to three status reports for your push request: a server-level acknowledgment, transport acknowledgment, and application-level acknowledgment. You can also query the status of a push request for a specific BlackBerry device.

Runs in the background

The Push Initiator sends content as bandwidth becomes available so that it doesn't interfere with other applications, such as phone calls.

Minimal battery drain

The Push Service minimizes the impact on device batteries because the push-enabled application listens in the background for the Push Initiator to send content to it. The application doesn't need to poll the push server for content.

Less coding

The Push Service SDK minimizes the amount of code that you need to write to create a Push Service solution. You can use the APIs in the server-side and client-side libraries to perform these common tasks:

  • Send, query, or cancel push messages
  • Specify listeners, acknowledgments and their notifications
  • Track completed push messages
  • Track the running count of push messages

Last modified: 2014-03-10

Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus