- From: Jonas Sicking <jonas@sicking.cc>
- Date: Wed, 20 Aug 2014 17:44:02 -0700
- To: "mark a. foltz" <mfoltz@google.com>
- Cc: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, Anton Vayvod <avayvod@google.com>, Marco Chen <mchen@mozilla.com>, Wesley Johnston <wjohnston@mozilla.com>, "public-webscreens@w3.org" <public-webscreens@w3.org>, Evelyn Hung <ehung@mozilla.com>
On Wed, Aug 20, 2014 at 5:30 PM, mark a. foltz <mfoltz@google.com> wrote: >> In order to make this flow slightly more efficient we could in step 8 >> include in the "onavailablechange" event include a flag indicating >> that a presentation for the same origin is already running. That way >> AwesomeGame could avoid doing step 9 in most cases when AwesomeGame >> wasn't running on the TV. > > I think the requestSession check should be able to be computed quickly > (either the browser is aware of the presentation or not) so perhaps this > isn't necessary. I don't feel strongly either way. Having the information available synchronously in the onavailablechange event handler (through a property) is somewhat simpler than enabling getting the information asynchronously (through a call to requestSession). But it doesn't make a big difference. We can certainly leave the property out for now, it's easier to add it later based on author feedback than to remove it later based on it not being used. / Jonas
Received on Thursday, 21 August 2014 00:45:00 UTC