JavaScript/HandlingThreads: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
In Firefox 4, JS extensions using nsIThread.dispatch won't work the same way they have in the past. The purpose of this page is to document the design choices we have, so we can get to a decision, late though it may be.
In Firefox 4, JS extensions using nsIThread.dispatch won't work the same way they have in the past. The purpose of this page is to document the design choices we have, so we can get to a decision, late though it may be.


# MT Proxies
Here are the choices we have. We can pick more than one.
# ChromeWorkers w/ usable Constructor
 
# Nothing
= MT Proxies =
# Environment cloning
=== Description ===
# structured cloning with WrappedNative handling
=== Advantages ===
=== Disadvantages ===
ChromeWorkers w/ usable Constructor =
=== Description ===
=== Advantages ===
=== Disadvantages ===
= Nothing =
=== Description ===
=== Advantages ===
=== Disadvantages ===
= Environment cloning =
=== Description ===
=== Advantages ===
=== Disadvantages ===
= structured cloning with WrappedNative handling =
=== Description ===
=== Advantages ===
=== Disadvantages ===

Revision as of 22:27, 16 November 2010

In Firefox 4, JS extensions using nsIThread.dispatch won't work the same way they have in the past. The purpose of this page is to document the design choices we have, so we can get to a decision, late though it may be.

Here are the choices we have. We can pick more than one.

MT Proxies

Description

Advantages

Disadvantages

ChromeWorkers w/ usable Constructor

Description

Advantages

Disadvantages

Nothing

Description

Advantages

Disadvantages

Environment cloning

Description

Advantages

Disadvantages

structured cloning with WrappedNative handling

Description

Advantages

Disadvantages