When I was documenting my first Service Worker I mentioned that every time a user requests a page, I store that page in a cache for later (offline) use:
Right now I’m stashing any HTML pages the user visits into the cache. I don’t think that will get out of control—I imagine most people only ever visit just a handful of pages on my site. But there’s the chance that the cache could get quite bloated. Ideally I’d have some way of keeping the cache nice and lean.
I was thinking: maybe I should have a separate cache for HTML pages, and limit the number in that cache to, say, 20 or 30 items. Every time I push something new into that cache, I could pop the oldest item out.
I could imagine doing something similar for images: keeping a cache of just the most recent 10 or 20.
Well I’ve done that now. Here’s the updated Service Worker code.
I’ve got a function in there called stashInCache that takes a few arguments: which cache to use, the maximum number of items that should be in there, the request (URL), and the response:
var stashInCache = function(cacheName, maxItems, request, response) {
caches.open(cacheName)
.then(function (cache) {
cache.keys()
.then(function (keys) {
if (keys.length < maxItems) {
cache.put(request, response);
} else {
cache.delete(keys[0])
.then(function() {
cache.put(request, response);
});
}
})
});
};
It looks to see if the current number of items in the cache is less than the specified maximum:
if (keys.length < maxItems)
If so, go ahead and cache the item:
cache.put(request, response);
Otherwise, delete the first item from the cache and then put the item in the cache:
cache.delete(keys[0])
.then(function() {
cache.put(request, response);
});
For HTML requests, I limit the cache to 35 items:
var copy = response.clone();
var cacheName = version + pagesCacheName;
var maxItems = 35;
stashInCache(cacheName, maxItems, request, copy);
return response;
For images, I’m limiting the cache to 20 items:
var copy = response.clone();
var cacheName = version + imagesCacheName;
var maxItems = 20;
stashInCache(cacheName, maxItems, request, copy);
return response;
Here’s my updated Service Worker.
The cache-limited seems to be working for pages. But for some reason the images cache has blown past its allotted maximum of 20 (you can see the items in the caches under the “Resources” tab in Chrome under “Cache Storage”).
This is almost certainly because I’m doing something wrong or have completely misunderstood how the caching works. If you can spot what I’m doing wrong, please let me know.
1 Like
# Liked by Front-End Front on Sunday, November 22nd, 2015 at 7:39pm