Confirmed users
214
edits
Media/WebRTC/Architecture: Difference between revisions
→Important threads
No edit summary |
|||
| Line 158: | Line 158: | ||
* PeerConnection Thread: the thread where the PeerConnection operates (new thread; QUESTION: how many are there? one total or one per PC?) | * 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). | * CCAPP_Task: the outermost of the SIPCC threads, running in <tt>ccapp_task.c:CCApp_task()</tt> (SIPCC thread). | ||
* Media Input Thread: the thread used by WebRTC for incoming media decoding (new thread) | |||
* Media Output Thread: the thread used by WebRTC for outgoing media encoding (new thread; may be the same as Media Input thread). | |||
Two notes about this: | |||
# In general, expensive operations prompted by (DOM, STS, MediaStream) need to be done on other threads, so your event handlers should just Dispatch to some other thread which does the work. This is particularly true for media encoding and decoding. | |||
# SIPCC has a pile of internal threads, but they are all front-ended by CCAPP_Task, so not our problem. | |||
=== Signaling System: CreateOffer === | === Signaling System: CreateOffer === | ||