From 8547118a52e4a85ce9fe395f493dd4cfece529df Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 25 Oct 2022 10:18:06 -0700 Subject: [PATCH] Change dmc urls to lmc, remove locale --- PushnotificationsDemo/Views/Home/Index.cshtml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PushnotificationsDemo/Views/Home/Index.cshtml b/PushnotificationsDemo/Views/Home/Index.cshtml index 40b38a7..c1975f9 100644 --- a/PushnotificationsDemo/Views/Home/Index.cshtml +++ b/PushnotificationsDemo/Views/Home/Index.cshtml @@ -150,7 +150,7 @@

To start, you’ll first need to make sure your web server is setup to send pushes. We’ll be using an ASP.NET Core server and take advantage of the open-source WebPush library so that we don’t have to worry about the encryption details involved with sending a push.

We’ll first need to call Install-Package WebPush (web push library) from a terminal or from the Package Manager so that we can use it in our app.

-

We’ll need to specify the VAPID keys that will allow identifications between our app’s server and the notification server (e.g. Firebase Cloud Messaging (FCM), Mozilla Cloud Services (MCS), and Windows Push Notification Service (WNS) depending on which browser is being used). You only need to set up the VAPID keys once which can be generated easily:

+

We’ll need to specify the VAPID keys that will allow identifications between our app’s server and the notification server (e.g. Firebase Cloud Messaging (FCM), Mozilla Cloud Services (MCS), and Windows Push Notification Service (WNS) depending on which browser is being used). You only need to set up the VAPID keys once which can be generated easily:

using WebPush;
 var vapidKeys = VapidHelper.GenerateVapidKeys();
@@ -316,7 +316,7 @@ function urlBase64ToUint8Array(base64String) {

The W3C Push API and Notification API go hand-in-hand to enable push notifications in modern browsers. The Push API is used to set up a push subscription and is invoked when a message is pushed to the corresponding service worker. The service worker then is responsible for showing a notification to the user using the Notification API and reacting to user interaction with the notification.

-

A standardized method of message delivery is also important for the W3C Push API to work consistently across all major browsers where application servers will need to use multiple push services. For instance, Google Chrome and Mozilla Firefox use Firebase Cloud Messaging (FCM) and Mozilla Cloud Services (MCS), respectively while Microsoft Edge relies on the Windows Push Notification Service (WNS) to deliver push messages. To reach reasonable interoperability with other browsers’ messaging services, WNS has now deployed support for the Web Push protocols being finalized within IETF, as well as the Message Encryption spec and the Voluntary Application Server Identification (VAPID) spec for web push. Web developers can now use the Web Push APIs and service workers to provide an interoperable push service on the web.

+

A standardized method of message delivery is also important for the W3C Push API to work consistently across all major browsers where application servers will need to use multiple push services. For instance, Google Chrome and Mozilla Firefox use Firebase Cloud Messaging (FCM) and Mozilla Cloud Services (MCS), respectively while Microsoft Edge relies on the Windows Push Notification Service (WNS) to deliver push messages. To reach reasonable interoperability with other browsers’ messaging services, WNS has now deployed support for the Web Push protocols being finalized within IETF, as well as the Message Encryption spec and the Voluntary Application Server Identification (VAPID) spec for web push. Web developers can now use the Web Push APIs and service workers to provide an interoperable push service on the web.