W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2014

Re: [whatwg] Proposal: requestBackgroundProcessing()

From: Glenn Maynard <glenn@zewt.org>
Date: Thu, 20 Feb 2014 15:55:52 -0600
Message-ID: <CABirCh919R-+B1xdYy0WJq_XXxMswNT=TyMnASGeOA+0ZUyoxw@mail.gmail.com>
To: Ashley Gullen <ashley@scirra.com>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Rik Cabanier <cabanier@gmail.com>, James Robinson <jamesr@google.com>
On Thu, Feb 20, 2014 at 3:29 PM, Ashley Gullen <ashley@scirra.com> wrote:

> There's a lot of worker features that aren't widely supported yet, like
> rendering to canvas with WebGL and 2D, Web Audio support, inputs, various
> APIs like speech and fullscreen, so I don't think that's practical right
> now. I guess that's not a reason to standardise a new feature, but is there
> not at least a workaround for the mean time? Are workers able to wake the
> UI with postMessage()?
>

You were talking about running the server of a multiplayer game.  Other
than communicating with other clients, it doesn't need any of that, right?
 Those are all client-side behaviors.

You can send a message to the UI thread.  I didn't suggest that, since it
feels like an arms race of trying to sidestep browser behavior.  It may not
matter, since the common things they're trying to stop are probably things
like never-ending animation timers running when you can't even see it (who
have no reason to drive their timers from a worker to bypass the timer
throttling), but I'd recommend trying to move your actual server logic into
a worker.

-- 
Glenn Maynard
Received on Thursday, 20 February 2014 21:56:24 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:16 UTC