[e] (0) add issue markers for sending structured data over postMessage

git-svn-id: http://svn.whatwg.org/webapps@1890 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jul 18, 2008 · ce2f2e4 · ce2f2e4
1 parent 24198bd
commit ce2f2e4
Show file tree

Hide file tree

Showing 2 changed files with 32 additions and 0 deletions.
diff --git a/index b/index
@@ -1631,6 +1631,9 @@
 
        <li><a href="#posting0"><span class=secno>7.4.4 </span>Posting message
         ports</a>
+
+       <li><a href="#posting1"><span class=secno>7.4.5 </span>Posting
+        structured data</a>
       </ul>
 
      <li><a href="#channel"><span class=secno>7.5 </span>Channel
@@ -42032,6 +42035,11 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
     <p>Send a 0xff byte to the server.
   </ol>
 
+  <p class=big-issue>People often request the ability to send binary blobs
+   over this API; also, once the other postMessage() methods support it, we
+   should look into allowing name/value pairs, arrays, and numbers using
+   postMessage() instead of just strings and binary data.
+
   <h5 id=server-side><span class=secno>7.3.4.2. </span>Server-side
    requirements</h5>
 
@@ -42468,6 +42476,11 @@ function receiver(e) {
   sections be kept separate so that implementors can avoid getting
   confused with the 'port' step. -->
 
+  <h4 id=posting1><span class=secno>7.4.5 </span>Posting structured data</h4>
+
+  <p class=big-issue>People often request the ability to send name/value
+   pairs, arrays, and numbers using postMessage() instead of just strings.
+
   <h3 id=channel><span class=secno>7.5 </span><dfn id=channel0>Channel
    messaging</dfn></h3>
 
@@ -42761,6 +42774,9 @@ function receiver(e) {
    <!-- XXX queue -->
   </ol>
 
+  <p class=big-issue>People often request the ability to send name/value
+   pairs, arrays, and numbers using postMessage() instead of just strings.
+
   <hr>
 
   <p>The <dfn id=close2

diff --git a/source b/source
@@ -39647,6 +39647,12 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
 
   </ol>
 
+  <p class="big-issue">People often request the ability to send binary
+  blobs over this API; also, once the other postMessage() methods
+  support it, we should look into allowing name/value pairs, arrays,
+  and numbers using postMessage() instead of just strings and binary
+  data.</p>
+
 
   <h5>Server-side requirements</h5>
 
@@ -40155,6 +40161,12 @@ function receiver(e) {
   confused with the 'port' step. -->
 
 
+  <h4>Posting structured data</h4>
+
+  <p class="big-issue">People often request the ability to send
+  name/value pairs, arrays, and numbers using postMessage() instead of
+  just strings.</p>
+
 
 
 
@@ -40428,6 +40440,10 @@ function receiver(e) {
 
   </ol>
 
+  <p class="big-issue">People often request the ability to send
+  name/value pairs, arrays, and numbers using postMessage() instead of
+  just strings.</p>
+
   <hr>
 
   <p>The <dfn title="dom-MessagePort-close"><code>close()</code></dfn>