- From: Andrew Fedoniouk <news@terrainformatica.com>
- Date: Sun, 20 Jul 2008 00:01:19 -0700
- To: Ian Hickson <ian@hixie.ch>
- CC: public-html@w3.org
Ian Hickson wrote: > On Sat, 19 Jul 2008, Andrew Fedoniouk wrote: >> Chapter: >> http://www.whatwg.org/specs/web-workers/current-work/#processing >> has following: >> .... >> #5 Let script's script execution context (and thus also global object) be >> worker. >> #6 Let script's script browsing context be owner browsing context. >> #7 Let script's script document context be owner document. >> .... >> >> But[1] tells us that: >> "A browsing context is a collection of one or more Document objects, and one >> or more views." >> >> Intention is to isolate Worker so it is not clear what #6 and #7 mean. > > They mean exactly what they say; Workers are "isolated" in a JavaScript > sense but this doesn't preclude them being associated with a particular > JavaScript browsing context. > Sorry but what exactly is that "browsing context"? Is it set of objects, interfaces or just such a smell? (For some reasons I found difficult for myself to understand language used in http://www.whatwg.org/specs/web-workers/ ,sorry again) > >> Also it is not clear how method: >> >> MessagePort createWorker(in DOMString scriptURL); >> >> downloads that script. If it is an asynchronous operation then it should >> be some event. If it is synchronous operation than it should be some >> timeout or so defined. > > It is downloaded in step 1 of the "run a worker" algorithm. > Is it list item #1 in: http://www.whatwg.org/specs/web-workers/current-work/#processing ? If "yes" then for me it contains only this: "Attempt to fetch the resource identified by url. If the attempt fails,.... If the attempt succeeds, then ...." Question is: how that Attempt is made exactly? Synchronously or asynchronously? -- Andrew Fedoniouk. http://terrainformatica.com
Received on Sunday, 20 July 2008 07:02:05 UTC