zoukankan      html  css  js  c++  java
  • [PWA] 2. Service worker life cycle

    1. Once serive worker is registered, the first time we go to the app, we cannot see the logs from servcie works. Any only refersh it second time, then we able to see the logs.
    2. Once we change service worker, it doesn't seem that we have change it.

    The No1. is because, service worker only take control after it is loaded. But the first time we go to the page, service worker actually is not there, because, the browser need to fetch our assets, css, and Javascript fiels which include our sw.js. So that's why the first time we go to page, we didn't see the logs. But after we refresh the page, the sw.js is already cached. So the service worker can control from now on.

    The No2. is because, once we change the code, it will check with service worker and if it is changed, it will become next version of serive worker. BUT it doesn't take control, it WATIS. It won't take control unitl all page use current version are gone. And a refresh doens't help, it because a overlap bewteen window client. Only you close the current page or naviagte to a page that isn't controlled by current service worker. When it does that, the new version of servie worker will take control.

    So if you change the code a little bit:

    self.addEventListener('fetch', function(event) {
      console.log("yo ",event.request);
    });

    And then close the current page, then open it again, you will see the new logs come out:

  • 相关阅读:
    Day 37 数据库初识
    Day 36 socket并发,协程,进程池与线程池
    Day 35 GIL全局解释器锁,死锁与递归锁,信号量,event事件,线程queue
    DAY 34 进程通信、消费者模型和线程
    09-盒模型
    08-层叠性权重相同处理
    07-css的继承性和层叠性
    06-伪元素选择器
    05-伪类选择器
    04-属性选择器
  • 原文地址:https://www.cnblogs.com/Answer1215/p/5496097.html
Copyright © 2011-2022 走看看