14137 2011-09-13 11:35:56 +0000 Just want to add - don't get hung up on the process/thread stuff. It is just a metaphor. I don't really care how it is implemented. One could do it all in one process. The present design fits the process model nicely. There is no sharing of memory. 2011-09-13 19:43:23 +0000 1 1 1 Unclassified WebAppsWG Web Workers (editor: Ian Hickson) unspecified Other other RESOLVED DUPLICATE 14086 http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian art.barstow ayg mike public-webapps public-webapps-bugzilla oldest_to_newest 56735 0 contributor 2011-09-13 11:35:56 +0000 Specification: http://www.w3.org/TR/2011/WD-workers-20110901/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Just want to add - don't get hung up on the process/thread stuff. It is just a metaphor. I don't really care how it is implemented. One could do it all in one process. The present design fits the process model nicely. There is no sharing of memory. However, the design decision to make the DOM inaccessible is, I hope I have shown, unnecessary. Regardless of how the browser is presently implemented (eg threads for Firefox), there IS a way to put in the DOM. Every browser that I know of can have two web pages open at once. Those 2 web pages both have a DOM, they don't share a DOM. Some browsers implement this as 2 different processes, some as 2 threads. The approach of having the web worker have a DOM seems to be the least amount of work to do for implementers, and does not give developers more strange rules to remember (oh yeah, I cannot user the window object, I cannot use the setInterval() or alert(), but wait, the W3C kludged some stuff on to allow me to do some of that)... Posted from: 199.89.158.132 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 56737 1 zcorpan 2011-09-13 12:19:17 +0000 *** This bug has been marked as a duplicate of bug 14086 *** 56757 2 ayg 2011-09-13 19:43:23 +0000 (In reply to comment #0) > Every browser that I know of can have two web pages open at once. Those 2 web > pages both have a DOM, they don't share a DOM. Some browsers implement this > as 2 different processes, some as 2 threads. This is where you're mistaken. Some browsers (Firefox?) have one thread for all pages. They cannot support two threads both accessing DOMs, even different DOMs, because their implementation is not thread-safe at all. Different pages can both access DOMs because they're actually on the same thread. (I think.)