- From: Wesley Johnston <wjohnston@mozilla.com>
- Date: Mon, 3 Mar 2014 08:29:20 -0800 (PST)
- To: Anssi Kostiainen <anssi.kostiainen@intel.com>
- Cc: public-webscreens@w3.org
Just glancing at this briefly, there's still nothing in the spec to describe how we would actually facilitate communication between two different UA's. i.e. UA1 calls postMessage() -> Magic happens -> UA2 receives onMessage We'd really like to avoid that sort of magic, and there are already specs (as I mentioned earlier, PeerConnection?) that do handle it. In the same way, if we're tackling two UA systems here, I think we also need to define how discovery and the initial setup of a connection between two UA's is handled. I'd like to avoid a situation where that communication has to be defined differently for each different type of device. I like the idea of using this as a way to make Network Discovery work, but I think we'd be hesitant about implementing anything until there were solutions to those problems. - Wes ----- Original Message ----- From: "Anssi Kostiainen" <anssi.kostiainen@intel.com> To: public-webscreens@w3.org Sent: Monday, March 3, 2014 7:46:15 AM Subject: Updated Presentation API WebIDL - call for review Hi All, As a group, we’ve now mulled over the design of the revised Presentation API by looking at the use cases, requirements, and concrete usage examples. As the concrete next step, we’ve drafted the WebIDL for the updated Presentation API, ready for your review at: https://www.w3.org/community/webscreens/wiki/API_Discussion#WebIDL All - please review the WebIDL and chime in on the list if you have any questions or concerns, big or small. Also, if you’re happy with the direction, positive signals are also encouraged, even if just +1s. As usual, silence is considered consent. Before we start land changes to the spec itself, we want to ensure we’re aligned, so your feedback at this stage is much appreciated. Thanks, -Anssi
Received on Monday, 3 March 2014 16:29:50 UTC