W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

[Bug 14137] New: 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.

From: <bugzilla@jessica.w3.org>
Date: Tue, 13 Sep 2011 11:35:56 +0000
To: public-webapps@w3.org
Message-ID: <bug-14137-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14137

           Summary: 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.
           Product: WebAppsWG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Web Workers (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


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

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 13 September 2011 11:36:02 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT