1016304 - Implement a Worker Transport

Status: RESOLVED WONTFIX

(DevTools :: General, defect)

Description

[Eddy Bruel [:ejpbruel]]

Bug 1003095 removed most chrome dependencies from the server (on those code paths we care about), but before we can move the server over to the worker thread we still need a transport that allows us to talk to the server over the worker's communication channel.

The plan is to create a transport that can talk to a MessagePort. We should then enable MessageChannel for chrome code (bug 984990).

If the worker loader is running on the main thread, it will use MessageChannel to create two MessagePorts. The server port will be exposed to the server as a per-module global, while the client port will be exposed as a property on the loader itself (the idea being that each worker loader represents/corresponds to a single worker). This should allow us to test the new transport without having to move everything over to the worker thread quite yet.

Comment 1

[Eddy Bruel [:ejpbruel]]

I'm closing this bug because it will be subsumed in a larger scoped bug that I'm about to open as a dependency for bug 1003097.