Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[giow] (0) Minor tweaks to PeerConnection to make it more usable
git-svn-id: http://svn.whatwg.org/webapps@5956 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Mar 18, 2011
1 parent 3bacb0d commit 6b0ec94
Show file tree
Hide file tree
Showing 3 changed files with 32 additions and 26 deletions.
20 changes: 11 additions & 9 deletions complete.html
Expand Up @@ -239,7 +239,7 @@

<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>Web Applications 1.0</h1>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 16 March 2011</h2>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 18 March 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
Expand Down Expand Up @@ -71668,7 +71668,7 @@ <h3 id=stream-api><span class=secno>9.3 </span>Stream API</h3>
&lt;p id="errorMessage"&gt;Loading...&lt;/p&gt;
&lt;/section&gt;
&lt;section id="app" hidden&gt;
&lt;p&gt;&lt;video id="monitor"&gt;&lt;/video&gt; &lt;canvas id="photo"&gt;&lt;/canvas&gt;
&lt;p&gt;&lt;video id="monitor" autoplay&gt;&lt;/video&gt; &lt;canvas id="photo"&gt;&lt;/canvas&gt;
&lt;p&gt;&lt;input type=button value="&amp;#x1F4F7;" onclick="snapshot()"&gt;
&lt;/section&gt;
&lt;script&gt;
Expand Down Expand Up @@ -71734,7 +71734,7 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec

[Callback=FunctionOnly, NoInterfaceObject]
interface <dfn id=signalingcallback>SignalingCallback</dfn> {
void <span title=dom-SignalingCallback-handleEvent>handleEvent</span>(in <a href=#peerconnection>PeerConnection</a> source, in DOMString message);
void <span title=dom-SignalingCallback-handleEvent>handleEvent</span>(in DOMString message, in <a href=#peerconnection>PeerConnection</a> source);
};</pre>

<p>A <code><a href=#peerconnection>PeerConnection</a></code> allows two users to communicate
Expand Down Expand Up @@ -71784,11 +71784,11 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec

</dl><p>The <var title="">signalingCallback</var> argument is a method
that will be invoked when the user agent needs to send a message
to the other host over the signaling channel. When the callback
is invoked, convey its 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>
to the other host over the signaling channel. When the callback is
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>
method.)</p>

</dd>
Expand Down Expand Up @@ -72078,7 +72078,8 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec
<li><p><a href=#queue-a-task>Queue a task</a> to invoke that
<a href=#peerconnection-ice-agent><code>PeerConnection</code> ICE Agent</a>'s
<a href=#peerconnection-signaling-callback><code>PeerConnection</code> signaling callback</a> with
<var title="">message</var> as its argument.</li>
<var title="">message</var> as its first argument and the
<code><a href=#peerconnection>PeerConnection</a></code> as its second argument.</li>

</ol><p>All streams represented by <code><a href=#stream>Stream</a></code> objects must be
marked as "sendonly" by the peer that initially adds the stream to
Expand Down Expand Up @@ -96432,6 +96433,7 @@ <h3 class="no-num">Reflecting IDL attributes</h3>
Olli Pettay,
oSand, <!-- from reddit -->
Patrick H. Lauke,
Patrik Persson,
Paul Norman,
Per-Erik Brodin,
Perry Smith,
Expand Down
20 changes: 11 additions & 9 deletions index
Expand Up @@ -243,7 +243,7 @@

<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 16 March 2011</h2>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 18 March 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
Expand Down Expand Up @@ -71677,7 +71677,7 @@ interface <dfn id=dom-url title=dom-URL>URL</dfn> {
&lt;p id="errorMessage"&gt;Loading...&lt;/p&gt;
&lt;/section&gt;
&lt;section id="app" hidden&gt;
&lt;p&gt;&lt;video id="monitor"&gt;&lt;/video&gt; &lt;canvas id="photo"&gt;&lt;/canvas&gt;
&lt;p&gt;&lt;video id="monitor" autoplay&gt;&lt;/video&gt; &lt;canvas id="photo"&gt;&lt;/canvas&gt;
&lt;p&gt;&lt;input type=button value="&amp;#x1F4F7;" onclick="snapshot()"&gt;
&lt;/section&gt;
&lt;script&gt;
Expand Down Expand Up @@ -71743,7 +71743,7 @@ interface <dfn id=peerconnection>PeerConnection</dfn> {

[Callback=FunctionOnly, NoInterfaceObject]
interface <dfn id=signalingcallback>SignalingCallback</dfn> {
void <span title=dom-SignalingCallback-handleEvent>handleEvent</span>(in <a href=#peerconnection>PeerConnection</a> source, in DOMString message);
void <span title=dom-SignalingCallback-handleEvent>handleEvent</span>(in DOMString message, in <a href=#peerconnection>PeerConnection</a> source);
};</pre>

<p>A <code><a href=#peerconnection>PeerConnection</a></code> allows two users to communicate
Expand Down Expand Up @@ -71793,11 +71793,11 @@ interface <dfn id=signalingcallback>SignalingCallback</dfn> {

</dl><p>The <var title="">signalingCallback</var> argument is a method
that will be invoked when the user agent needs to send a message
to the other host over the signaling channel. When the callback
is invoked, convey its 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>
to the other host over the signaling channel. When the callback is
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>
method.)</p>

</dd>
Expand Down Expand Up @@ -72087,7 +72087,8 @@ interface <dfn id=signalingcallback>SignalingCallback</dfn> {
<li><p><a href=#queue-a-task>Queue a task</a> to invoke that
<a href=#peerconnection-ice-agent><code>PeerConnection</code> ICE Agent</a>'s
<a href=#peerconnection-signaling-callback><code>PeerConnection</code> signaling callback</a> with
<var title="">message</var> as its argument.</li>
<var title="">message</var> as its first argument and the
<code><a href=#peerconnection>PeerConnection</a></code> as its second argument.</li>

</ol><p>All streams represented by <code><a href=#stream>Stream</a></code> objects must be
marked as "sendonly" by the peer that initially adds the stream to
Expand Down Expand Up @@ -92557,6 +92558,7 @@ interface <a href=#htmldocument>HTMLDocument</a> {
Olli Pettay,
oSand, <!-- from reddit -->
Patrick H. Lauke,
Patrik Persson,
Paul Norman,
Per-Erik Brodin,
Perry Smith,
Expand Down
18 changes: 10 additions & 8 deletions source
Expand Up @@ -81766,7 +81766,7 @@ interface <dfn title="dom-URL">URL</dfn> {
&lt;p id="errorMessage">Loading...&lt;/p>
&lt;/section>
&lt;section id="app" hidden>
&lt;p>&lt;video id="monitor">&lt;/video> &lt;canvas id="photo">&lt;/canvas>
&lt;p>&lt;video id="monitor" autoplay>&lt;/video> &lt;canvas id="photo">&lt;/canvas>
&lt;p>&lt;input type=button value="&amp;#x1F4F7;" onclick="snapshot()">
&lt;/section>
&lt;script>
Expand Down Expand Up @@ -81832,7 +81832,7 @@ interface <dfn>PeerConnection</dfn> {

[Callback=FunctionOnly, NoInterfaceObject]
interface <dfn>SignalingCallback</dfn> {
void <span title="dom-SignalingCallback-handleEvent">handleEvent</span>(in <span>PeerConnection</span> source, in DOMString message);
void <span title="dom-SignalingCallback-handleEvent">handleEvent</span>(in DOMString message, in <span>PeerConnection</span> source);
};</pre>

<p>A <code>PeerConnection</code> allows two users to communicate
Expand Down Expand Up @@ -81893,11 +81893,11 @@ interface <dfn>SignalingCallback</dfn> {

<p>The <var title="">signalingCallback</var> argument is a method
that will be invoked when the user agent needs to send a message
to the other host over the signaling channel. When the callback
is invoked, convey its 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
to the other host over the signaling channel. When the callback is
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">signalingMessage()</code>
method.)</p>

Expand Down Expand Up @@ -82231,7 +82231,8 @@ interface <dfn>SignalingCallback</dfn> {
<li><p><span>Queue a task</span> to invoke that
<span><code>PeerConnection</code> ICE Agent</span>'s
<span><code>PeerConnection</code> signaling callback</span> with
<var title="">message</var> as its argument.</p></li>
<var title="">message</var> as its first argument and the
<code>PeerConnection</code> as its second argument.</p></li>

</ol>

Expand Down Expand Up @@ -109922,6 +109923,7 @@ interface <span>HTMLDocument</span> {
Olli Pettay,
oSand, <!-- from reddit -->
Patrick H. Lauke,
Patrik Persson,
Paul Norman,
Per-Erik Brodin,
Perry Smith,
Expand Down

0 comments on commit 6b0ec94

Please sign in to comment.