MICROSOFT_PRESS_EBOOK_PROGRAMMING_WINDOWS_8_APPS_WITH_HTML_CSS_AND_JAVASCRIPT_PDF

In the running app, the pushnotificationreceived event is fired for the other notification types as
well. Scenario 3 of the sample shows this in its event handler—I’ve modified this code a little bit for
simplicity:
function startListening() {
// Assume channel has been obtained and validated
channel.addEventListener("pushnotificationreceived", pushNotificationReceivedHandler);
}
function pushNotificationReceivedHandler(e) {
// Extract notification payload for each notification type
var notificationPayload;
switch (e.notificationType) {
case pushNotifications.PushNotificationType.toast:
notificationPayload = e.toastNotification.content.getXml();
break;
case pushNotifications.PushNotificationType.tile:
notificationPayload = e.tileNotification.content.getXml();
break;
case pushNotifications.PushNotificationType.badge:
notificationPayload = e.badgeNotification.content.getXml();
break;
}
case pushNotifications.PushNotificationType.raw:
notificationPayload = e.rawNotification.content;
break;
}
// Process the notification: set e.cancel to true to suppress automatic handling.
The last bit in the comment above is important. When you receive this event in a running app, it
wouldn’t be necessary to display a toast unless it pertains to some other part of the app that isn’t visible.
For example, if you have an app that handles both email and a calendar, you might want to show email
toasts when the user is looking at the calendar and calendar toasts when the user is looking at email. In
this case, setting e.cancel to true will suppress the toast.
With the pushnotificationreceived event, the running apps gets first crack at raw notifications. If
the app doesn’t process it, the notification will be sent to any lock screen background task configured
for the PushNotificationTrigger. In either case, refer to the Raw notifications sample for more details.
613