The Windows Push Notification Services (WNS) enables third-party developers to send toast, tile, and badge updates from their own cloud service. This provides a mechanism to deliver new updates to your users in a dependable and power-efficient way. The topics in this section show you code examples that demonstrate how to accomplish specific tasks that relate to the sending of push notifications.
See the push notification overview for a conceptual discussion of push notification and WNS concepts, requirements, and operation. See Windows Azure Mobile Services to learn about using Windows Azure to send notifications.
In this section
| Topic | Description |
|---|---|
|
Your cloud server can send a push notification to your app through the WNS. This procedure applies to tile, toast, badge, and raw push notifications. | |
|
You can open a channel Uniform Resource Identifier (URI) over which your app can receive push notifications. You can then send the channel to your server which uses it to send push notifications, and close it when you no longer need it. | |
|
How to authenticate with the Windows Push Notification Service (WNS) |
This topic explains how to authenticate your cloud server with WNS and receive an access token in return. |
|
This topic describes the service-to-service web APIs and protocols required to send a push notification. | |
|
Quickstart: Intercepting push notifications for running apps |
You can design your app to intercept a push notification and respond to that notification in a non-default manner. This procedure can be used for all push notification types, but it is particularly useful for toast and raw notifications. |
|
You can use raw notifications, a type of push notification, to send short messages from your app's cloud service to an app through WNS. Unlike the XML payload of other push notification types (tile, toast, badge), the payload contained in a raw notification is strictly app-defined, and is not used to convey UI data. |
Build date: 11/29/2012
