Confirmed users
214
edits
Media/WebRTC/WebRTCE10S: Difference between revisions
Jump to navigation
Jump to search
→Introduction
| Line 17: | Line 17: | ||
and between the PeerConnection and video/audio tags. This doesn't mean that | and between the PeerConnection and video/audio tags. This doesn't mean that | ||
the media actually flows through the JS, however. | the media actually flows through the JS, however. | ||
== System Resources to be Proxied == | |||
The following system resources need to somehow be made accessible to the renderer | |||
process. | |||
* Video rendering (accessed via a video tag) <i>[TODO: Is this actually a system resource? Not clear on what | |||
the display model is.]</i> | |||
* The speaker (accessed via an audio tag) | |||
* The camera and microphone | |||
* Hardware video encoders and decoders (if any) | |||
* The network interfaces | |||
In addition, we use the Socket Transport Service (STS) to do socket input processing. We create | |||
UDP sockets via NSPR and then attach them to the STS in order to be informed when data is | |||
available. | |||