Service workers and base URIs

Previously when we've run into a contentious service worker design issue, we've asked web developers what they think. This has worked out pretty well in the past, with developer feedback directly informing spec changes. It's also great because we can blame y'all if you pick the wrong thing.

Well, it's that time again! Help us!

Read on…

2016 - the year of web streams

Yeah, ok, it's a touch bold to talk about something being the thing of the year as early as January, but the potential of the web streams API has gotten me all excited.

Streams can be used to do fun things like turn clouds to butts, transcode MPEG to GIF, but most importantly, they can be combined with service workers to become the fastest way to serve content.

Read on…

Tasks, microtasks, queues and schedules

When I told my colleague Matt Gaunt I was thinking of writing a piece on microtask queueing and execution within the browser's event loop, he said "I'll be honest with you Jake, I'm not going to read that". Well, I've written it anyway, so we're all going to sit here and enjoy it, ok?

Read on…

The offline cookbook

ServiceWorker brief overview gives you control over caching and how requests are handled. It doesn't give you patterns, you create them yourself. Let's look at a few!

Read on…

Iterators gonna iterate

ES6 gives us a new way to iterate, and it's already supported in stable releases of Firefox, Chrome, & Opera. Here it is…

Read on…

Launching ServiceWorker without breaking the web

With ServiceWorkers you can control requests to any page on your origin, and any of the subresource requests made by those pages. This is powerful stuff, and I'm curious to know what security measure you think is appropriate…

Read on…

  1. Previous
  2. 1
  3. 2
  4. 3