Media/WebRTC/Architecture: Difference between revisions

Jump to navigation Jump to search

Media/WebRTC/Architecture (view source)

Revision as of 22:36, 19 August 2012

597 bytes removed ,  19 August 2012
no edit summary
No edit summary
Line 253: Line 253:


Note that real care will need to be taken to make sure that the lifetime of objects shared across threads is right. We should be using nsRefPtr with thread-safe ref count objects to assist this process.
Note that real care will need to be taken to make sure that the lifetime of objects shared across threads is right. We should be using nsRefPtr with thread-safe ref count objects to assist this process.
== Open Issues ==
* Do we have one set of worker threads (PC, Media In, Media Out) per call? One per origin? One total?
* Who is responsible for cleaning up the various objects? My thought is that SIPCC creates and deletes most things, but that makes using ref counted pointers a bit harder (Though not impossible).
* Are the media input and output streams separate or distinct?
* Where is DTLS processing (which is interlocked with the DTLS state machine) done? It's easiest to do this on STS as is ordinarily done with SSL/TLS. Is this too expensive. Note that this is only for Data Channels.
Ekr
Confirmed users
214

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/462238"

Navigation menu