- From: Drew Wilson <atwilson@google.com>
- Date: Fri, 11 Feb 2011 18:24:30 -0800
I'll mention that the Chrome team is experimenting with something like this
(as a Chrome extensions API) - certain extensions will be able to do:
window.open("my_bg_page.html", "name", "background");
...and the associated window will be opened offscreen. They share a process
with other pages under that domain which means they can't be used as a
worker (doing long-lived operations). But I agree, there's some value in
having the full set of page APIs available.
-atw
On Fri, Feb 11, 2011 at 5:58 PM, Gregg Tavares (wrk) <gman at google.com>wrote:
> On Fri, Feb 11, 2011 at 5:45 PM, Ian Hickson <ian at hixie.ch> wrote:
>
> > On Fri, 11 Feb 2011, Gregg Tavares (wrk) wrote:
> > > > On Fri, 7 Jan 2011, Berend-Jan Wever wrote:
> > > > >
> > > > > 1) To give WebWorkers access to the DOM API so they can create
> their
> > > > > own elements such as img, canvas, etc...?
> > > >
> > > > It's the API itself that isn't thread-safe, unfortunately.
> > >
> > > I didn't see the original thread but how is a WebWorker any different
> > > from another webpage? Those run just fine in other threads and use the
> > > DOM API.
> >
> > Web pages do not run in a different thread.
> >
>
> Oh, sorry. I meant they run in a different process. At least in some
> browsers.
>
>
> >
> > --
> > Ian Hickson U+1047E )\._.,--....,'``. fL
> > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
> > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
> >
>
Received on Friday, 11 February 2011 18:24:30 UTC