Confirmed users
214
edits
Media/WebRTC/Architecture: Difference between revisions
no edit summary
No edit summary |
|||
| Line 150: | Line 150: | ||
=== Important threads === | === Important threads === | ||
There are a number of threads that do the heavy lifting here. | |||
* DOM Thread: the thread where calls from the JS end up executing. Anything running here blocks the DOM and the JS engine (existing Firefox thread) | |||
* SocketTRansportService (STS): the thread with the main networking event loop (existing Firefox thread) | |||
* MediaStream: where media from devices is delivered. (same as DOM thread?) (existing Firefox thread) | |||
* PeerConnection Thread: the thread where the PeerConnection operates (new thread; QUESTION: how many are there? one total or one per PC?) | |||
* CCAPP_Task: the outermost of the SIPCC threads, running in <tt>ccapp_task.c:CCApp_task()</tt> (SIPCC thread). | |||
=== Signaling System: CreateOffer === | === Signaling System: CreateOffer === | ||