How do Chrome notifications work internally?











up vote
0
down vote

favorite












I recently learnt how mobile push notifications work but did not get any relevant tutorial how push notifications work on the Chrome browser.



Here is my understanding how Chrome notifications must be working based on mobile notifications. But I'm not sure what the device_id in chrome
/browser notification is? Is it some unique chrome_id or mac_id?



I need to work on Android mobile push notification. I have recently gone through some of the tutorials on Google. I would like to summarize my understandings first:




  1. A developer registers the web app with Chrome cloud service (is it also called GCM i.e. Google Cloud Messaging service?) and get some unique code called Application_Id

  2. Once the end user opens the web application, the client side code asks the user whether he/she would like to register for notifications. If he/she says yes, some unique id may be chrome_id or mac_id is sent to to GCM and GCM generates the unique token and sent back to the Chrome hosting web app.

  3. The client browser sends back that token to the back-end server which keeps that token along with user details

  4. Now whenever the back-end needs to send a notification to the user, it will send to GCM along with a token which GCM will forward to Chrome.


Is that correct?



Question:




  1. What is the device_id in case of Chrome?

  2. Is the role of GCM stated above correct?

  3. Do I need to register web application with GCM as mentioned in step_1 ?










share|improve this question






















  • I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
    – Felipe Morales
    Nov 4 at 19:46















up vote
0
down vote

favorite












I recently learnt how mobile push notifications work but did not get any relevant tutorial how push notifications work on the Chrome browser.



Here is my understanding how Chrome notifications must be working based on mobile notifications. But I'm not sure what the device_id in chrome
/browser notification is? Is it some unique chrome_id or mac_id?



I need to work on Android mobile push notification. I have recently gone through some of the tutorials on Google. I would like to summarize my understandings first:




  1. A developer registers the web app with Chrome cloud service (is it also called GCM i.e. Google Cloud Messaging service?) and get some unique code called Application_Id

  2. Once the end user opens the web application, the client side code asks the user whether he/she would like to register for notifications. If he/she says yes, some unique id may be chrome_id or mac_id is sent to to GCM and GCM generates the unique token and sent back to the Chrome hosting web app.

  3. The client browser sends back that token to the back-end server which keeps that token along with user details

  4. Now whenever the back-end needs to send a notification to the user, it will send to GCM along with a token which GCM will forward to Chrome.


Is that correct?



Question:




  1. What is the device_id in case of Chrome?

  2. Is the role of GCM stated above correct?

  3. Do I need to register web application with GCM as mentioned in step_1 ?










share|improve this question






















  • I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
    – Felipe Morales
    Nov 4 at 19:46













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I recently learnt how mobile push notifications work but did not get any relevant tutorial how push notifications work on the Chrome browser.



Here is my understanding how Chrome notifications must be working based on mobile notifications. But I'm not sure what the device_id in chrome
/browser notification is? Is it some unique chrome_id or mac_id?



I need to work on Android mobile push notification. I have recently gone through some of the tutorials on Google. I would like to summarize my understandings first:




  1. A developer registers the web app with Chrome cloud service (is it also called GCM i.e. Google Cloud Messaging service?) and get some unique code called Application_Id

  2. Once the end user opens the web application, the client side code asks the user whether he/she would like to register for notifications. If he/she says yes, some unique id may be chrome_id or mac_id is sent to to GCM and GCM generates the unique token and sent back to the Chrome hosting web app.

  3. The client browser sends back that token to the back-end server which keeps that token along with user details

  4. Now whenever the back-end needs to send a notification to the user, it will send to GCM along with a token which GCM will forward to Chrome.


Is that correct?



Question:




  1. What is the device_id in case of Chrome?

  2. Is the role of GCM stated above correct?

  3. Do I need to register web application with GCM as mentioned in step_1 ?










share|improve this question













I recently learnt how mobile push notifications work but did not get any relevant tutorial how push notifications work on the Chrome browser.



Here is my understanding how Chrome notifications must be working based on mobile notifications. But I'm not sure what the device_id in chrome
/browser notification is? Is it some unique chrome_id or mac_id?



I need to work on Android mobile push notification. I have recently gone through some of the tutorials on Google. I would like to summarize my understandings first:




  1. A developer registers the web app with Chrome cloud service (is it also called GCM i.e. Google Cloud Messaging service?) and get some unique code called Application_Id

  2. Once the end user opens the web application, the client side code asks the user whether he/she would like to register for notifications. If he/she says yes, some unique id may be chrome_id or mac_id is sent to to GCM and GCM generates the unique token and sent back to the Chrome hosting web app.

  3. The client browser sends back that token to the back-end server which keeps that token along with user details

  4. Now whenever the back-end needs to send a notification to the user, it will send to GCM along with a token which GCM will forward to Chrome.


Is that correct?



Question:




  1. What is the device_id in case of Chrome?

  2. Is the role of GCM stated above correct?

  3. Do I need to register web application with GCM as mentioned in step_1 ?







google-chrome web-applications push-notification






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 4 at 9:49









user3198603

1,34652250




1,34652250












  • I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
    – Felipe Morales
    Nov 4 at 19:46


















  • I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
    – Felipe Morales
    Nov 4 at 19:46
















I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
– Felipe Morales
Nov 4 at 19:46




I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
– Felipe Morales
Nov 4 at 19:46

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53139520%2fhow-do-chrome-notifications-work-internally%23new-answer', 'question_page');
}
);

Post as a guest





































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53139520%2fhow-do-chrome-notifications-work-internally%23new-answer', 'question_page');
}
);

Post as a guest




















































































這個網誌中的熱門文章

Xamarin.form Move up view when keyboard appear

Post-Redirect-Get with Spring WebFlux and Thymeleaf

Anylogic : not able to use stopDelay()