You need to
before you can comment on or make changes to this bug.
It should be possible to create new Workers from Workers.
The main low-level functionality that is still missing is an ability to load resources from Workers, same as in XMLhttpRequest and importScripts().
*** Bug 25152 has been marked as a duplicate of this bug. ***
Assigning to Jian Li because of all the work done in blocking bugs.
Sorry for asking this question relatively late in the game, but what are the use cases for nested workers? Do they warrant increased complexity in the existing and future (e.g. Web Inspector) code at this point?
Creating workers from workers doesn't seem to be a dangerous feature, and it seems potentially useful, but it is not clear to me if it's useful enough to add yet, without feedback from web application authors who use workers.
I think they're quite useful in developing a large web application. For example, an online email application can start a worker to fetch emails and store them in the local storage on the background. This worker can start a couple nested workers such that some actions can be done in parallel, like using XHR to send emails and receive emails. With nested worker support, it will become easier to write such big applications.
If you need more information on this. Please ping me.
*** Bug 24016 has been marked as a duplicate of this bug. ***
Note: Firefox 3.5 has launched with support for this. Over lunch today, I chatted with Maciej about this and he supported the view that we should be at feature parity to avoid developer confusion.
Does chromium have a plan to do that?
Where can find detailed information?
Thanks in advance.
I don't know about current plans but usually it was a question if there is enough real world need to justify the work... The work can be non-trivial, some part include loading refactoring (currently delegated to the parent, assuming it's a Page) and perhaps things like DevTools integration... In the past, the folks involved found more pressing needs to work on, that's it.
Theoretically, it's a nice feature and it's in the spec :-)
I am working on a library to support communication with sandboxed code that is agnostic to the specific sandboxing mechanism used. See https://github.com/tildeio/oasis.js
Support for nested contexts is important for this library (and the use-cases that are driving it).