- From: Jungkee Song <notifications@github.com>
- Date: Thu, 19 May 2016 03:32:40 -0700
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc:
Received on Thursday, 19 May 2016 10:33:14 UTC
> so we could generate an ID that we then later use once the client is created. This is what I suggested. 1. Navigation is triggered. 1. [Navigation] Invoke fetch. 1. [Fetch] Invoke Handle Fetch. 1. [Handle Fetch] Create (potential) target client information 1. [Navigation] Create (target) Window/Document 1. [Navigation] Set Window/Document's client information to the value created in 4. In order to do that, the step 4 and 6 above should be added. And for this, I wanted to have some internal slots for id and active worker on a fetch algorithm instance or on a request. > How does this work in browsers today? Blink creates some corresponding state (object) when fetch occurs, and the properties in that object are later associated with the the page/worker. So, largely the steps I suggest here is what the implementation does now. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/870#issuecomment-220287341
Received on Thursday, 19 May 2016 10:33:14 UTC