- From: Andrew Sutherland <notifications@github.com>
- Date: Sun, 15 Sep 2019 11:16:20 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 15 September 2019 18:16:42 UTC
The `await worker.exports` sounds like it would need to be a middle-ware right now because of the mismatch between the capabilities of what exports can expose and what structured serialization can encode over the wire. That said, it sounds like Typed Objects https://github.com/tschneidereit/proposal-typed-objects/blob/master/explainer.md are going to happen because of WASM needs. I don't think the explainer goes into it, but my understanding was that these typed objects could enable concurrent multi-threaded access as well as be transferrable via structured serialization (and cheaply!). So they could form the basis of something easy to spec if the spec is "only typed objects can be exported by a worker top-level script" and then the fact that all typed objects can be cloned/serialized means there's no problems with things that don't serialize. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1387#issuecomment-531587425
Received on Sunday, 15 September 2019 18:16:42 UTC