- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 18 Jan 2012 22:57:07 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/postmsg
In directory hutz:/tmp/cvs-serv26570
Modified Files:
Overview.html
Log Message:
Add more explanatory text about postMessage()'s first argument. (whatwg r6903)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/postmsg/Overview.html,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -d -r1.112 -r1.113
--- Overview.html 7 Dec 2011 23:24:23 -0000 1.112
+++ Overview.html 18 Jan 2012 22:57:04 -0000 1.113
@@ -215,12 +215,13 @@
<h1>HTML5 Web Messaging</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-7-december-2011">Editor's Draft 7 December 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-18-january-2012">Editor's Draft 18 January 2012</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/webmessaging/">http://www.w3.org/TR/webmessaging/</a></dd>
<dt>Latest Editor's Draft:</dt>
<dd><a class="latest-link" href="http://dev.w3.org/html5/postmsg/">http://dev.w3.org/html5/postmsg/</a></dd>
+
<dt>Previous Versions:</dt>
<dd><a href="http://www.w3.org/TR/2010/WD-webmessaging-20101118/">http://www.w3.org/TR/2010/WD-webmessaging-20101118/</a></dd>
<!-- :ZZZ -->
@@ -317,7 +318,7 @@
</dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications
Working Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation track.
- This specification is the 7 December 2011 Editor's Draft.
+ This specification is the 18 January 2012 Editor's Draft.
</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/42538/status" rel="disclosure">public list of
any patent disclosures</a> made in connection with the deliverables
@@ -326,6 +327,7 @@
individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
6 of the W3C Patent Policy</a>.<h2 class="no-num no-toc" id="contents">Table of Contents</h2>
+
<ol class="toc">
<li><a href="#conformance-requirements"><span class="secno">1 </span>Conformance requirements</a>
<ol>
@@ -603,8 +605,16 @@
<dd>
- <p>Posts a message to the given window. Objects listed in <var title="">transfer</var> are transferred, not just cloned, meaning
- that they are no longer usable on the sending side.</p>
+ <p>Posts a message to the given window. Messages can be structured
+ objects, e.g. nested objects and arrays, can contain JavaScript
+ values (strings, numbers, <code>Date</code>s, etc), and can
+ contain certain data objects such as <code>File</code>
+ <code>Blob</code>, <code>FileList</code>, and
+ <code>ArrayBuffer</code> objects.</p>
+
+ <p>Objects listed in <var title="">transfer</var> are transferred,
+ not just cloned, meaning that they are no longer usable on the
+ sending side.</p>
<p>If the origin of the target window doesn't match the given
origin, the message is discarded, to avoid information leakage. To
@@ -767,6 +777,7 @@
<a href="#refsHTML">[HTML]</a>
</p>
+
</li>
<li>
@@ -790,7 +801,8 @@
function handleMessage(event) {
// message is in event.data
// ...
-}</pre><h4 id="ports-as-the-basis-of-an-object-capability-model-on-the-web"><span class="secno">5.1.1 </span>Ports as the basis of an object-capability model on the Web</h4><p><i>This section is non-normative.</i><p>Ports can be viewed as a way to expose limited capabilities (in
+}</pre><p>Data sent on a port can be structured data; for example here an
+ array of strings is passed:<pre>port1.postMessage(['hello', 'world'], 'http://example.com');</pre><h4 id="ports-as-the-basis-of-an-object-capability-model-on-the-web"><span class="secno">5.1.1 </span>Ports as the basis of an object-capability model on the Web</h4><p><i>This section is non-normative.</i><p>Ports can be viewed as a way to expose limited capabilities (in
the object-capability model sense) to other actors in the system.
This can either be a weak capability system, where the ports are
merely used as a convenient model within a particular origin, or as
@@ -921,7 +933,8 @@
</div><h3 id="message-ports"><span class="secno">5.3 </span>Message ports</h3><p>Each channel has two message ports. Data sent through one port is
received by the other port, and vice versa.<pre class="idl">interface <dfn id="messageport">MessagePort</dfn> : <span>EventTarget</span> {
- void <a href="#dom-messageport-postmessage" title="dom-MessagePort-postMessage">postMessage</a>(any message, optional sequence<<span>Transferable</span>> transfer); void <a href="#dom-messageport-start" title="dom-MessagePort-start">start</a>();
+ void <a href="#dom-messageport-postmessage" title="dom-MessagePort-postMessage">postMessage</a>(any message, optional sequence<<span>Transferable</span>> transfer);
+ void <a href="#dom-messageport-start" title="dom-MessagePort-start">start</a>();
void <a href="#dom-messageport-close" title="dom-MessagePort-close">close</a>();
// event handlers
@@ -1133,6 +1146,7 @@
<li><p>If there is no <var title="">target port</var> (i.e. if <var title="">source port</var> is not entangled), then abort these
steps.</li>
+
<li><p>Create an event that uses the <code><a href="#messageevent">MessageEvent</a></code>
interface, with the name <code title="event-message"><a href="#event-message">message</a></code>, which does not bubble, is not
cancelable, and has no default action.
@@ -1210,7 +1224,9 @@
open and there exists a <code title="event-message"><a href="#event-message">message</a></code>
event in that queue.</p>
+
+
</div><p class="note">Authors are strongly encouraged to explicitly close
<code><a href="#messageport">MessagePort</a></code> objects to disentangle them, so that their
resources can be recollected. Creating many <code><a href="#messageport">MessagePort</a></code>
@@ -1219,7 +1235,8 @@
<dd><cite><a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html">Web DOM Core</a></cite>, A. van Kesteren. W3C.</dd>
<dt id="refsEVENTSOURCE">[EVENTSOURCE]</dt>
- <dd><cite><a href="http://dev.w3.org/html5/eventsource/">Server-Sent
+
+ <dd><cite><a href="http://dev.w3.org/html5/eventsource/">Server-Sent
Events</a></cite>, I. Hickson. W3C.</dd>
<dt id="refsHTML">[HTML]</dt>
@@ -1232,7 +1249,8 @@
RFCs to Indicate Requirement Levels</a></cite>, S. Bradner. IETF.</dd>
<dt id="refsWEBIDL">[WEBIDL]</dt>
- <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
+
+ <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
IDL</a></cite>, C. McCormack. W3C.</dd>
<dt id="refsWEBSOCKET">[WEBSOCKET]</dt>
Received on Wednesday, 18 January 2012 22:57:08 UTC