Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031)

As an implementation note, I likely will have to do something like:

1. Create the reserved Client object before the initial network request.
2. On redirect mutate the existing Client object to the new origin/URL/ID and wipe any pending messages.
3. Freeze the origin/URL/ID once the Client is marked as execution ready.

I don't like this, but due to a number of implementation details its very very racy to handle redirects for worker threads any other way.  The redirects happen on a different thread altogether.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1031#issuecomment-268809346