Re: [w3c/ServiceWorker] Should a service worker be able to block with shared memory APIs? (#1115) from Luke Wagner on 2017-04-18 (public-webapps-github@w3.org from April 2017)

From: Luke Wagner <notifications@github.com>
Date: Tue, 18 Apr 2017 07:13:07 -0700
To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/ServiceWorker/issues/1115/294857495@github.com>

Right now the atomics are only just being [proposed](https://github.com/WebAssembly/design/pull/10190) so it's not an issue we're dealing with yet.  Looks like @lars-t-hansen just brought up this question in that PR.  I would think that we'd just have the `wait` and `wake` opcodes trap (throw a `WebAssembly.RuntimeError`) if !AgentCanSuspend.  WebAssembly wouldn't be disabled, though.

-- 
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/1115#issuecomment-294857495

Received on Tuesday, 18 April 2017 14:13:40 UTC