- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Fri, 21 Feb 2014 14:18:12 +1300
- To: Ashley Gullen <ashley@scirra.com>
- Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Glenn Maynard <glenn@zewt.org>, Rik Cabanier <cabanier@gmail.com>, James Robinson <jamesr@google.com>
On Fri, Feb 21, 2014 at 11:32 AM, Ashley Gullen <ashley@scirra.com> wrote: > One solution is to make web workers able to access many of the same APIs > the UI thread can, especially with WebGL, Web Audio, WebRTC and rAF. Then > it might be practical to move a full game engine in to a worker. If that is > planned, I guess there is no need for a new feature. > Having (some form of) all these APIs available in a Worker is a long-term goal, but as Glenn just pointed out, it sounds like you could just run the server in a Worker and the rest of the engine on the main thread. Having said that, your server would want WebRTC DataChannels on the worker, and we don't have that yet. You can work around it by proxying messages to the main thread; postMessage from a Worker to the main thread is usually not throttled. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w
Received on Friday, 21 February 2014 01:18:37 UTC