WebRTC Introduction

  • Enlace amigable (slug) de la revisión: WebRTC/Introduction
  • Título de la revisión: WebRTC Introduction
  • Id de la revisión: 455959
  • Creada:
  • Creador: voylinux
  • ¿Es la revisión actual? No
  • Comentario

Contenido de la revisión

WebRTC te permite establecer una comunicación punto-a-punto en una aplicación del navegador.

Estableciendo la conexión

The initial connection between peers must be accomplished via an application server that provides for user discovery, communication, and Network Address Translation (NAT) with data streaming.

Signalling

Signalling is the mechanism by which peers send control messages to each other for the purpose of establishing the communication protocol, channel, and method. These are not specified in the WebRTC standard. Rather, the developer may choose any messaging protocol (such as SIP or XMPP), and any two-way communication channel (such as WebSocket or XMLHttpRequest) in tandem with a persistent connection server API (like the Google Channel API) for AppEngine.

Transmission

getUserMedia

LocalMediaStream object

Reception

WebRTC support in Firefox is hidden behind a preference switch. Go to about:config and set 'media.navigator.enabled' to 'true'.

There are some test files in the source tree to give you an idea what things work. See: dom/media/tests/local_video_test.html. Please also try the call service demo, its page source, and its server source.

 

Fuente de la revisión

<div class="note">
  <p>WebRTC te permite establecer una comunicación punto-a-punto en una aplicación del navegador.</p>
</div>
<h2 id="Estableciendo_la_conexi.C3.B3n">Estableciendo la conexión</h2>
<p>The initial connection between peers must be accomplished via an application server that provides for user discovery, communication, and Network Address Translation (NAT) with data streaming.</p>
<h3 id="Signalling">Signalling</h3>
<p>Signalling is the mechanism by which peers send control messages to each other for the purpose of establishing the communication protocol, channel, and method. These are not specified in the WebRTC standard. Rather, the developer may choose any messaging protocol (such as SIP or XMPP), and any two-way communication channel (such as WebSocket or XMLHttpRequest) in tandem with a persistent connection server API (like the <a href="https://developers.google.com/appengine/docs/python/channel/overview" title="https://developers.google.com/appengine/docs/python/channel/overview">Google Channel API</a>) for AppEngine.</p>
<h2 id="Transmission">Transmission</h2>
<h3 id="getUserMedia">getUserMedia</h3>
<p>LocalMediaStream object</p>
<h2 id="Reception">Reception</h2>
<p>WebRTC support in Firefox is hidden behind a preference switch. Go to <a href="/about:config" title="/about:config">about:config</a> and set 'media.navigator.enabled' to 'true'.</p>
<div class="note">
  <p>There are some test files in the source tree to give you an idea what things work. See: <a href="http://hg.mozilla.org/projects/alder/file/tip/dom/media/tests/local_video_test.html">dom/media/tests/local_video_test.html</a>. Please also try the <a href="http://webrtc-demo.herokuapp.com/mozdemo">call service demo</a>, its page source, and its <a href="https://github.com/anantn/webrtc-demo/">server source</a>.</p>
</div>
<p>&nbsp;</p>
Revertir a esta revisión