Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
[giow] (0) Use 'message' instead of 'text' for the event name for con…
- Loading branch information
Showing
with
12 additions
and
12 deletions.
-
+4
−4
complete.html
-
+4
−4
index
-
+4
−4
source
|
|
|
|
|
|
|
|
// <span class=XXX>connection quality information</span> |
|
|
|
|
|
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-ontext title=handler-PeerConnection-ontext>ontext</a>; |
|
|
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onmessage title=handler-PeerConnection-onmessage>onmessage</a>; |
|
|
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onaddstream title=handler-PeerConnection-onaddstream>onaddstream</a>; |
|
|
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onremovestream title=handler-PeerConnection-onremovestream>onremovestream</a>; |
|
|
}; |
|
|
|
|
|
every message will be received.</p> |
|
|
|
|
|
<p>When a message sent in this manner from the other peer is |
|
|
received, a <code title=event-PeerConnection-text>text</code> |
|
|
received, a <code title=event-PeerConnection-message>message</code> |
|
|
event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p> |
|
|
|
|
|
</dd> |
|
|
|
|
|
interface:</p> |
|
|
|
|
|
<table><thead><tr><th><a href=#event-handlers title="event handlers">Event handler</a> <th><a href=#event-handler-event-type>Event handler event type</a> |
|
|
<tbody><tr><td><dfn id=handler-peerconnection-ontext title=handler-PeerConnection-ontext><code>ontext</code></dfn> <td> <code title=event-stream-text>text</code> |
|
|
<tbody><tr><td><dfn id=handler-peerconnection-onmessage title=handler-PeerConnection-onmessage><code>onmessage</code></dfn> <td> <code title=event-stream-message>message</code> |
|
|
<tr><td><dfn id=handler-peerconnection-onaddstream title=handler-PeerConnection-onaddstream><code>onaddstream</code></dfn> <td> <code title=event-stream-addstream>addstream</code> |
|
|
<tr><td><dfn id=handler-peerconnection-onremovestream title=handler-PeerConnection-onremovestream><code>onremovestream</code></dfn> <td> <code title=event-stream-removestream>removestream</code> |
|
|
</table><hr><p>The <a href=#task-source>task source</a> for the <a href=#concept-task title=concept-task>tasks</a> listed in this section is the |
|
|
|
|
|
handling</a>.</li> |
|
|
|
|
|
<li><p>Create an event that uses the <code><a href=#messageevent>MessageEvent</a></code> |
|
|
interface, with the name <code title=event-text>text</code>, |
|
|
interface, with the name <code title=event-message><a href=#event-message>message</a></code>, |
|
|
which does not bubble, is not cancelable, has no default action, |
|
|
and has a <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code> attribute |
|
|
whose value is <var title="">message</var>, and <a href=#queue-a-task>queue a |
|
|
|
|
|
|
|
|
// <span class=XXX>connection quality information</span> |
|
|
|
|
|
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-ontext title=handler-PeerConnection-ontext>ontext</a>; |
|
|
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onmessage title=handler-PeerConnection-onmessage>onmessage</a>; |
|
|
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onaddstream title=handler-PeerConnection-onaddstream>onaddstream</a>; |
|
|
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onremovestream title=handler-PeerConnection-onremovestream>onremovestream</a>; |
|
|
}; |
|
|
|
|
|
every message will be received.</p> |
|
|
|
|
|
<p>When a message sent in this manner from the other peer is |
|
|
received, a <code title=event-PeerConnection-text>text</code> |
|
|
received, a <code title=event-PeerConnection-message>message</code> |
|
|
event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p> |
|
|
|
|
|
</dd> |
|
|
|
|
|
interface:</p> |
|
|
|
|
|
<table><thead><tr><th><a href=#event-handlers title="event handlers">Event handler</a> <th><a href=#event-handler-event-type>Event handler event type</a> |
|
|
<tbody><tr><td><dfn id=handler-peerconnection-ontext title=handler-PeerConnection-ontext><code>ontext</code></dfn> <td> <code title=event-stream-text>text</code> |
|
|
<tbody><tr><td><dfn id=handler-peerconnection-onmessage title=handler-PeerConnection-onmessage><code>onmessage</code></dfn> <td> <code title=event-stream-message>message</code> |
|
|
<tr><td><dfn id=handler-peerconnection-onaddstream title=handler-PeerConnection-onaddstream><code>onaddstream</code></dfn> <td> <code title=event-stream-addstream>addstream</code> |
|
|
<tr><td><dfn id=handler-peerconnection-onremovestream title=handler-PeerConnection-onremovestream><code>onremovestream</code></dfn> <td> <code title=event-stream-removestream>removestream</code> |
|
|
</table><hr><p>The <a href=#task-source>task source</a> for the <a href=#concept-task title=concept-task>tasks</a> listed in this section is the |
|
|
|
|
|
handling</a>.</li> |
|
|
|
|
|
<li><p>Create an event that uses the <code><a href=#messageevent>MessageEvent</a></code> |
|
|
interface, with the name <code title=event-text>text</code>, |
|
|
interface, with the name <code title=event-message><a href=#event-message>message</a></code>, |
|
|
which does not bubble, is not cancelable, has no default action, |
|
|
and has a <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code> attribute |
|
|
whose value is <var title="">message</var>, and <a href=#queue-a-task>queue a |
|
|
|
|
|
|
|
|
// <span class="XXX">connection quality information</span> |
|
|
|
|
|
attribute <span>Function</span> <span title="handler-PeerConnection-ontext">ontext</span>; |
|
|
attribute <span>Function</span> <span title="handler-PeerConnection-onmessage">onmessage</span>; |
|
|
attribute <span>Function</span> <span title="handler-PeerConnection-onaddstream">onaddstream</span>; |
|
|
attribute <span>Function</span> <span title="handler-PeerConnection-onremovestream">onremovestream</span>; |
|
|
}; |
|
|
|
|
|
every message will be received.</p> |
|
|
|
|
|
<p>When a message sent in this manner from the other peer is |
|
|
received, a <code title="event-PeerConnection-text">text</code> |
|
|
received, a <code title="event-PeerConnection-message">message</code> |
|
|
event is dispatched at the <code>PeerConnection</code> object.</p> |
|
|
|
|
|
</dd> |
|
|
|
|
|
<thead> |
|
|
<tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span> |
|
|
<tbody> |
|
|
<tr><td><dfn title="handler-PeerConnection-ontext"><code>ontext</code></dfn> <td> <code title="event-stream-text">text</code> |
|
|
<tr><td><dfn title="handler-PeerConnection-onmessage"><code>onmessage</code></dfn> <td> <code title="event-stream-message">message</code> |
|
|
<tr><td><dfn title="handler-PeerConnection-onaddstream"><code>onaddstream</code></dfn> <td> <code title="event-stream-addstream">addstream</code> |
|
|
<tr><td><dfn title="handler-PeerConnection-onremovestream"><code>onremovestream</code></dfn> <td> <code title="event-stream-removestream">removestream</code> |
|
|
</table> |
|
|
|
|
|
handling</span>.</p></li> |
|
|
|
|
|
<li><p>Create an event that uses the <code>MessageEvent</code> |
|
|
interface, with the name <code title="event-text">text</code>, |
|
|
interface, with the name <code title="event-message">message</code>, |
|
|
which does not bubble, is not cancelable, has no default action, |
|
|
and has a <code title="dom-MessageEvent-data">data</code> attribute |
|
|
whose value is <var title="">message</var>, and <span>queue a |
