brozek/website
1
0
Fork 0
mirror of https://github.com/Brandon-Rozek/website.git synced 2025-10-09 22:41:13 +00:00
Code Issues Projects Releases Packages Activity

Cleaned up posts

Browse source
This commit is contained in:
Brandon Rozek 2022-11-22 22:24:43 -05:00
parent e357c43f0f
commit ccc51022ac
2 changed files with 21 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/blog/2015-11-30-limiting-cache-service-workers-revisited3.md
View file

@ -36,7 +36,7 @@ I wrote a function in my [previous service worker post](https://brandonrozek.com
```javascript
var limitCache = function(cache, maxItems) {
cache.keys().then(function(items) {
if (items.length > maxItems) {
if (items.length > maxItems) {
cache.delete(items[0]);
}
})
@ -97,7 +97,7 @@ Once it receives the command, it goes on to trim all of the caches.
### Conclusion
So whenever you download a bunch of files, make sure to run <code class="language-javascript">navigator.serviceWorker.controller.postMessage({"command":"trimCache"});</code> on the main javascript file to trim the cache. A downside to this method is that since Service Workers don&#8217;t take control during the first page load, the cache isn&#8217;t trimmed until the second page load. If you can find a way to make it so that this event happens in the first page load [tell me](mailto:hello@brandonrozek.com) about it/write a blog post. 🙂 **Update:** To get the service worker to take control of the page immediately call [self.skipWaiting()](https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerGlobalScope/skipWaiting) after the install event and [self.clients.claim()](https://developer.mozilla.org/en-US/docs/Web/API/Clients/claim) after the activate event. Current code for our humble service worker:
So whenever you download a bunch of files, make sure to run `navigator.serviceWorker.controller.postMessage({"command":"trimCache"});` on the main javascript file to trim the cache. A downside to this method is that since Service Workers don&#8217;t take control during the first page load, the cache isn&#8217;t trimmed until the second page load. If you can find a way to make it so that this event happens in the first page load [tell me](mailto:hello@brandonrozek.com) about it/write a blog post. 🙂 **Update:** To get the service worker to take control of the page immediately call [self.skipWaiting()](https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerGlobalScope/skipWaiting) after the install event and [self.clients.claim()](https://developer.mozilla.org/en-US/docs/Web/API/Clients/claim) after the activate event. Current code for our humble service worker:
```javascript
var version = 'v2.0.24:';
@ -149,7 +149,7 @@ var trimCache = function (cacheName, maxItems) {
.then(function (cache) {
cache.keys()
.then(function (keys) {
if (keys.length &gt; maxItems) {
if (keys.length > maxItems) {
cache.delete(keys[0])
.then(trimCache(cacheName, maxItems));
}