- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Sep 2015 09:36:26 +0000
- To: public-secondscreen@w3.org
The TAG prepared a draft review of the Presentation API. The relevant part appears more descriptive than prescriptive: [[ The spec describes launching a new browsing context to the presentation display. Given the spec as written, it does not appear as if this is a client/server channel, but rather a client/client (peer) channel. The back-channel, maintained by the user agent for client/client browsing context communications (like those of window.open ) is currently not defined other than to say that a message passing system (like postMessage ) must guarantee in-order delivery. If the presentation on the second screen communicates with its server (it is loaded via the presentationURL ), then the send() API is unnecessary to the feature, as pre-existing client/server communication API fill this gap ( WebSocket , XMLHttpRequest , etc.) ]] https://github.com/w3ctag/spec-reviews/blob/master/2015/presentation-api.md -- GitHub Notif of comment by tidoust See https://github.com/w3c/presentation-api/issues/80#issuecomment-140686834
Received on Wednesday, 16 September 2015 09:36:28 UTC