[html5] r6293 - [giow] (0) Rename signalingMessage() for clarity.
whatwg at whatwg.org
whatwg at whatwg.org
Tue Jul 12 16:54:54 PDT 2011
Author: ianh
Date: 2011-07-12 16:54:53 -0700 (Tue, 12 Jul 2011)
New Revision: 6293
Modified:
complete.html
index
source
Log:
[giow] (0) Rename signalingMessage() for clarity.
Modified: complete.html
===================================================================
--- complete.html 2011-07-12 22:40:27 UTC (rev 6292)
+++ complete.html 2011-07-12 23:54:53 UTC (rev 6293)
@@ -76015,7 +76015,7 @@
<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 @@
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 @@
</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 @@
</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
Modified: index
===================================================================
--- index 2011-07-12 22:40:27 UTC (rev 6292)
+++ index 2011-07-12 23:54:53 UTC (rev 6293)
@@ -75913,7 +75913,7 @@
<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 @@
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 @@
</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 @@
</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
Modified: source
===================================================================
--- source 2011-07-12 22:40:27 UTC (rev 6292)
+++ source 2011-07-12 23:54:53 UTC (rev 6293)
@@ -86721,7 +86721,7 @@
<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 @@
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 @@
</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 @@
</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>
More information about the Commit-Watchers
mailing list