W3C home > Mailing lists > Public > public-secondscreen@w3.org > September 2015

Re: [presentation-api] Define security requirements for messaging channel between secure origins

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Wed, 16 Sep 2015 09:36:26 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-140686834-1442396185-sysbot+gh@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.)

GitHub Notif of comment by tidoust
Received on Wednesday, 16 September 2015 09:36:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 16 September 2015 09:36:29 UTC