{"action":"created","issue":{"url":"https://api.github.com/repos/tc39/ecmascript_sharedmem/issues/57","repository_url":"https://api.github.com/repos/tc39/ecmascript_sharedmem","labels_url":"https://api.github.com/repos/tc39/ecmascript_sharedmem/issues/57/labels{/name}","comments_url":"https://api.github.com/repos/tc39/ecmascript_sharedmem/issues/57/comments","events_url":"https://api.github.com/repos/tc39/ecmascript_sharedmem/issues/57/events","html_url":"https://github.com/tc39/ecmascript_sharedmem/issues/57","id":131153960,"number":57,"title":"Allowance of signals from main thread to be passed via futexWake","user":{"login":"taisel","id":13305116,"avatar_url":"https://avatars.githubusercontent.com/u/13305116?v=3","gravatar_id":"","url":"https://api.github.com/users/taisel","html_url":"https://github.com/taisel","followers_url":"https://api.github.com/users/taisel/followers","following_url":"https://api.github.com/users/taisel/following{/other_user}","gists_url":"https://api.github.com/users/taisel/gists{/gist_id}","starred_url":"https://api.github.com/users/taisel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/taisel/subscriptions","organizations_url":"https://api.github.com/users/taisel/orgs","repos_url":"https://api.github.com/users/taisel/repos","events_url":"https://api.github.com/users/taisel/events{/privacy}","received_events_url":"https://api.github.com/users/taisel/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-03T21:08:09Z","updated_at":"2016-02-10T09:01:02Z","closed_at":"2016-02-10T08:20:59Z","body":"I'm opening as a question to determine the full impact and issue spectrum of using futexWake to proxy eventing signals from main thread to webworkers. Namely, to decide if there's any signals that should be prohibited from propagation or throttled for host computer power/efficiency reasons, or to prohibit improper eventing techniques for events that should exist within a webworker itself.\r\n\r\nThis question was brought up after slight discussion on the implications of requestAnimationFrame existing on main thread and not webworkers temporarily, and the impact that will cause for developers trying to find alternative solutions that are not ideal (or more power hungry)."},"comment":{"url":"https://api.github.com/repos/tc39/ecmascript_sharedmem/issues/comments/182262642","html_url":"https://github.com/tc39/ecmascript_sharedmem/issues/57#issuecomment-182262642","issue_url":"https://api.github.com/repos/tc39/ecmascript_sharedmem/issues/57","id":182262642,"user":{"login":"taisel","id":13305116,"avatar_url":"https://avatars.githubusercontent.com/u/13305116?v=3","gravatar_id":"","url":"https://api.github.com/users/taisel","html_url":"https://github.com/taisel","followers_url":"https://api.github.com/users/taisel/followers","following_url":"https://api.github.com/users/taisel/following{/other_user}","gists_url":"https://api.github.com/users/taisel/gists{/gist_id}","starred_url":"https://api.github.com/users/taisel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/taisel/subscriptions","organizations_url":"https://api.github.com/users/taisel/orgs","repos_url":"https://api.github.com/users/taisel/repos","events_url":"https://api.github.com/users/taisel/events{/privacy}","received_events_url":"https://api.github.com/users/taisel/received_events","type":"User","site_admin":false},"created_at":"2016-02-10T09:01:02Z","updated_at":"2016-02-10T09:01:02Z","body":"The question is asking whether or not there's power efficiency concerns that should be looked into, via possibly prohibiting some signalling. The idea that brought up this question was the setInterval clamping to 1000 milliseconds that vendors do when a webpage is hidden. There may be techniques that subvert such clamping with the webworker/sharedmemory API model."}}