{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 兄弟一词,经得起流年. 的问题《Is Service Worker intended to replace or coexist w》','https://www.manongdao.com/q-211505.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Is ServiceWorker intended to replace Appcache, or is the intention that the two will coexist? Phrased another way, is appcache about to become deprecated?
相关问题
- PWAs on iOS 12 no longer shares Service Worker cac
- Are promises lazily evaluated?
- start_url does not respond with a 200 when offline
- Adding a new header to a Request, while preserving
- unable to post message to service worker because c
相关文章
- HTML5 control
- Checking for service worker updates in a single pa
- Uncaught (in promise) DOMException: Quota exceeded
- Manifest start_url is not cached by a Service Work
- Why does fetch request have to be cloned in servic
- AppCache Manifest Error
- Get page URL parameters from a service worker
- How to remove a service worker registered in previ
Blink's Service Worker team is keen on deprecating AppCache (We will follow our usual intent to deprecate process). We believe that Service Worker is a much better solution. Also, it should be pretty easy to offer a drop-in replacement for AppCache built on top of SW. We'll start by collecting usage metrics and do some outreach.
AppCache and Service Worker should coexist without any issue since offering offline support via AppCache for browsers that don't support Service Workers is a valid use case. @flo850 If it's not working, please let us know by filing a bug.
As a cache tool, it will coexist with appcache. Appcache works on virtually every browser.
But service workers are a solid foundation that will permit new usage like push (even when the browser is in the background) , geofencing or background synchronization.
I must say that
Services Worker is not only the replacement for AppCache, but it’s far more capable.An AppCache can’t be partially updated, a byte-by-byte manifest comparison to trigger the update seems odd and there are several use cases leading to security and terrible usability problems.Even Chrome and Firefox are planning to stop support for AppCache in the near future. Now that service workers are supported by Chrome, Opera, and Firefox.Also, The noises coming from Microsoft and Safari have been positive with respect to implementation and under consideration.