Confirmed users, Bureaucrats and Sysops emeriti
291
edits
No edit summary |
|||
| Line 20: | Line 20: | ||
=== Disadvantages === | === Disadvantages === | ||
= Structured cloning with WrappedNative sharing = | = Structured cloning with WrappedNative sharing = | ||
= structured cloning with WrappedNative handling = | |||
=== Description === | === Description === | ||
In addition to chrome workers with a working constructor, we could add support for structured cloning of wrapped natives. | |||
=== Advantages === | === Advantages === | ||
This would allow a programming style that is more similar to what worked before with Thread.dispatch. Thread-safe C++ objects could be sent across to a different thread using postMessage and then operated on there. | |||
=== Disadvantages === | === Disadvantages === | ||
Implementation cost. | |||