The Windows Push Notification Services (WNS) enables you to send tile, badge, and toast notifications from the cloud. WNS provides a mechanism to deliver updates as necessary to your users, even when your app is not running. Push notifications are ideal when you need to target a specific user with personalized content.
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 |
|---|---|
|
This functionality would not typically be implemented using JavaScript. | |
|
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. |
|
This topic describes best practices for using push notifications and lists any requirements your app needs to meet to be accepted in the Windows Store. | |
|
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
