This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14137 - 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.
Summary: Just want to add - don't get hung up on the process/thread stuff. It is just...
Status: RESOLVED DUPLICATE of bug 14086
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Web Workers (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: public-webapps-bugzilla
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-13 11:35 UTC by contributor
Modified: 2011-09-13 19:43 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2011-09-13 11:35:56 UTC 
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
Comment 1 Simon Pieters 2011-09-13 12:19:17 UTC 

*** This bug has been marked as a duplicate of bug 14086 ***
Comment 2 Aryeh Gregor 2011-09-13 19:43:23 UTC 
(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.)