[giow] (0) Rename signalingMessage() for clarity.

git-svn-id: http://svn.whatwg.org/webapps@6293 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jul 12, 2011 · 696e62b · 696e62b
1 parent 20c43b8
commit 696e62b
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 16 deletions.
diff --git a/complete.html b/complete.html
@@ -76015,7 +76015,7 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec
 
   <pre class=idl>[<a href=#dom-peerconnection title=dom-PeerConnection>Constructor</a>(in DOMString configuration, in <a href=#signalingcallback>SignalingCallback</a> signalingCallback)]
 interface <dfn id=peerconnection>PeerConnection</dfn> {
-  void <a href=#dom-peerconnection-signalingmessage title=dom-PeerConnection-signalingMessage>signalingMessage</a>(in DOMString message);
+  void <a href=#dom-peerconnection-processsignalingmessage title=dom-PeerConnection-processSignalingMessage>processSignalingMessage</a>(in DOMString message);
 
   const unsigned short <a href=#dom-peerconnection-new title=dom-PeerConnection-NEW>NEW</a> = 0;
   const unsigned short <a href=#dom-peerconnection-negotiating title=dom-PeerConnection-NEGOTIATING>NEGOTIATING</a> = 1;
@@ -76098,7 +76098,7 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec
     invoked, convey its first argument (a string) to the other peer
     using whatever method is being used by the Web application to
     relay signaling messages. (Messages returned from the other peer
-    are provided back to the user agent using the <code title=dom-PeerConnection-signalingMessage><a href=#dom-peerconnection-signalingmessage>signalingMessage()</a></code>
+    are provided back to the user agent using the <code title=dom-PeerConnection-processSignalingMessage><a href=#dom-peerconnection-processsignalingmessage>processSignalingMessage()</a></code>
     method.)</p>
 
    </dd>
@@ -76119,13 +76119,13 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec
     </dl></dd>
 
 
-   <dt><var title="">connection</var> . <code title=dom-PeerConnection-signalingMessage><a href=#dom-peerconnection-signalingmessage>signalingMessage</a></code>(<var title="">message</var>)</dt>
+   <dt><var title="">connection</var> . <code title=dom-PeerConnection-processSignalingMessage><a href=#dom-peerconnection-processsignalingmessage>processSignalingMessage</a></code>(<var title="">message</var>)</dt>
 
    <dd>
 
     <p>When a message is relayed from the remote peer over the
     signaling channel is received by the Web application, pass it to
-    the user agent by calling the <code title=dom-PeerConnection-signalingMessage><a href=#dom-peerconnection-signalingmessage>signalingMessage()</a></code>
+    the user agent by calling the <code title=dom-PeerConnection-processSignalingMessage><a href=#dom-peerconnection-processsignalingmessage>processSignalingMessage()</a></code>
     method.</p>
 
     <p>The order of messages is important. Passing messages to the
@@ -76498,7 +76498,7 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec
 
     </ol></li>
 
-  </ol><p>When the <dfn id=dom-peerconnection-signalingmessage title=dom-PeerConnection-signalingMessage><code title="">signalingMessage()</code></dfn> method is invoked, the
+  </ol><p>When the <dfn id=dom-peerconnection-processsignalingmessage title=dom-PeerConnection-processSignalingMessage><code title="">processSignalingMessage()</code></dfn> method is invoked, the
   user agent must run the following steps:</p>
 
   <ol><li><p>Let <var title="">message</var> be the method's

diff --git a/index b/index
@@ -75913,7 +75913,7 @@ interface <dfn id=dom-url title=dom-URL>URL</dfn> {
 
   <pre class=idl>[<a href=#dom-peerconnection title=dom-PeerConnection>Constructor</a>(in DOMString configuration, in <a href=#signalingcallback>SignalingCallback</a> signalingCallback)]
 interface <dfn id=peerconnection>PeerConnection</dfn> {
-  void <a href=#dom-peerconnection-signalingmessage title=dom-PeerConnection-signalingMessage>signalingMessage</a>(in DOMString message);
+  void <a href=#dom-peerconnection-processsignalingmessage title=dom-PeerConnection-processSignalingMessage>processSignalingMessage</a>(in DOMString message);
 
   const unsigned short <a href=#dom-peerconnection-new title=dom-PeerConnection-NEW>NEW</a> = 0;
   const unsigned short <a href=#dom-peerconnection-negotiating title=dom-PeerConnection-NEGOTIATING>NEGOTIATING</a> = 1;
@@ -75996,7 +75996,7 @@ interface <dfn id=signalingcallback>SignalingCallback</dfn> {
     invoked, convey its first argument (a string) to the other peer
     using whatever method is being used by the Web application to
     relay signaling messages. (Messages returned from the other peer
-    are provided back to the user agent using the <code title=dom-PeerConnection-signalingMessage><a href=#dom-peerconnection-signalingmessage>signalingMessage()</a></code>
+    are provided back to the user agent using the <code title=dom-PeerConnection-processSignalingMessage><a href=#dom-peerconnection-processsignalingmessage>processSignalingMessage()</a></code>
     method.)</p>
 
    </dd>
@@ -76017,13 +76017,13 @@ interface <dfn id=signalingcallback>SignalingCallback</dfn> {
     </dl></dd>
 
 
-   <dt><var title="">connection</var> . <code title=dom-PeerConnection-signalingMessage><a href=#dom-peerconnection-signalingmessage>signalingMessage</a></code>(<var title="">message</var>)</dt>
+   <dt><var title="">connection</var> . <code title=dom-PeerConnection-processSignalingMessage><a href=#dom-peerconnection-processsignalingmessage>processSignalingMessage</a></code>(<var title="">message</var>)</dt>
 
    <dd>
 
     <p>When a message is relayed from the remote peer over the
     signaling channel is received by the Web application, pass it to
-    the user agent by calling the <code title=dom-PeerConnection-signalingMessage><a href=#dom-peerconnection-signalingmessage>signalingMessage()</a></code>
+    the user agent by calling the <code title=dom-PeerConnection-processSignalingMessage><a href=#dom-peerconnection-processsignalingmessage>processSignalingMessage()</a></code>
     method.</p>
 
     <p>The order of messages is important. Passing messages to the
@@ -76396,7 +76396,7 @@ interface <dfn id=signalingcallback>SignalingCallback</dfn> {
 
     </ol></li>
 
-  </ol><p>When the <dfn id=dom-peerconnection-signalingmessage title=dom-PeerConnection-signalingMessage><code title="">signalingMessage()</code></dfn> method is invoked, the
+  </ol><p>When the <dfn id=dom-peerconnection-processsignalingmessage title=dom-PeerConnection-processSignalingMessage><code title="">processSignalingMessage()</code></dfn> method is invoked, the
   user agent must run the following steps:</p>
 
   <ol><li><p>Let <var title="">message</var> be the method's

diff --git a/source b/source
@@ -86721,7 +86721,7 @@ interface <dfn title="dom-URL">URL</dfn> {
 
   <pre class="idl">[<span title="dom-PeerConnection">Constructor</span>(in DOMString configuration, in <span>SignalingCallback</span> signalingCallback)]
 interface <dfn>PeerConnection</dfn> {
-  void <span title="dom-PeerConnection-signalingMessage">signalingMessage</span>(in DOMString message);
+  void <span title="dom-PeerConnection-processSignalingMessage">processSignalingMessage</span>(in DOMString message);
 
   const unsigned short <span title="dom-PeerConnection-NEW">NEW</span> = 0;
   const unsigned short <span title="dom-PeerConnection-NEGOTIATING">NEGOTIATING</span> = 1;
@@ -86816,7 +86816,7 @@ interface <dfn>SignalingCallback</dfn> {
     using whatever method is being used by the Web application to
     relay signaling messages. (Messages returned from the other peer
     are provided back to the user agent using the <code
-    title="dom-PeerConnection-signalingMessage">signalingMessage()</code>
+    title="dom-PeerConnection-processSignalingMessage">processSignalingMessage()</code>
     method.)</p>
 
    </dd>
@@ -86839,14 +86839,14 @@ interface <dfn>SignalingCallback</dfn> {
    </dd>
 
 
-   <dt><var title="">connection</var> . <code title="dom-PeerConnection-signalingMessage">signalingMessage</code>(<var title="">message</var>)</dt>
+   <dt><var title="">connection</var> . <code title="dom-PeerConnection-processSignalingMessage">processSignalingMessage</code>(<var title="">message</var>)</dt>
 
    <dd>
 
     <p>When a message is relayed from the remote peer over the
     signaling channel is received by the Web application, pass it to
     the user agent by calling the <code
-    title="dom-PeerConnection-signalingMessage">signalingMessage()</code>
+    title="dom-PeerConnection-processSignalingMessage">processSignalingMessage()</code>
     method.</p>
 
     <p>The order of messages is important. Passing messages to the
@@ -87294,8 +87294,8 @@ interface <dfn>SignalingCallback</dfn> {
 
   </ol>
 
-  <p>When the <dfn title="dom-PeerConnection-signalingMessage"><code
-  title="">signalingMessage()</code></dfn> method is invoked, the
+  <p>When the <dfn title="dom-PeerConnection-processSignalingMessage"><code
+  title="">processSignalingMessage()</code></dfn> method is invoked, the
   user agent must run the following steps:</p>
 
   <ol>