gecko/media/mtransport
2013-08-22 08:56:00 +02:00
..
build Bug 883284 - Part e: Move LIBXUL_LIBRARY into moz.build (k-o); r=ted 2013-08-22 08:56:00 +02:00
standalone Bug 889572 - Remove EXPORTS from media/mtransport/standalone; r=gps 2013-07-09 13:49:38 -04:00
test Bug 882859 - Part b: Move FAIL_ON_WARNINGS into moz.build; r=joey+gps 2013-08-22 08:55:59 +02:00
third_party Bug 807492 Part 1.2 - Enable to build media/mtransport on BSD, #defines & #include bits r=abr 2013-08-13 23:59:57 +02:00
databuffer.h
dtlsidentity.cpp Bug 889615 - Add Granular logging to Mediapipeline. r=abr 2013-07-03 11:40:36 -07:00
dtlsidentity.h
gonk_addrs.cpp
logging.h Bug 889615 - Add Granular logging to Mediapipeline. r=abr 2013-07-03 11:40:36 -07:00
m_cpp_utils.h
nr_socket_prsock.cpp Bug 884061 - Part 3o: Use NS_DECL_THREADSAFE_ISUPPORTS in media/, r=abr 2013-07-18 21:23:32 -05:00
nr_socket_prsock.h Bug 884061 - Part 3o: Use NS_DECL_THREADSAFE_ISUPPORTS in media/, r=abr 2013-07-18 21:23:32 -05:00
nr_timer.cpp Bug 884061 - Part 3o: Use NS_DECL_THREADSAFE_ISUPPORTS in media/, r=abr 2013-07-18 21:23:32 -05:00
nricectx.cpp Bug 889615 - Add Granular logging to Mediapipeline. r=abr 2013-07-03 11:40:36 -07:00
nricectx.h
nricemediastream.cpp Bug 889615 - Add Granular logging to Mediapipeline. r=abr 2013-07-03 11:40:36 -07:00
nricemediastream.h
nriceresolver.cpp Bug 884061 - Part 3o: Use NS_DECL_THREADSAFE_ISUPPORTS in media/, r=abr 2013-07-18 21:23:32 -05:00
nriceresolver.h Bug 884061 - Part 3o: Use NS_DECL_THREADSAFE_ISUPPORTS in media/, r=abr 2013-07-18 21:23:32 -05:00
nriceresolverfake.cpp
nriceresolverfake.h
objs.mk Bug 807492 Part 1.1 - Allow to build media/mtransport on BSD, build bits r=jesup 2013-08-13 23:58:42 +02:00
README
runnable_utils_generated.h
runnable_utils.h
runnable_utils.py
sigslot.h
transportflow.cpp Bug 889615 - Add Granular logging to Mediapipeline. r=abr 2013-07-03 11:40:36 -07:00
transportflow.h
transportlayer.cpp Bug 889615 - Add Granular logging to Mediapipeline. r=abr 2013-07-03 11:40:36 -07:00
transportlayer.h
transportlayerdtls.cpp Bug 823338 - Fix incorrect check for OOM conditions in TransportLayerDtls::GetClientAuthDataHook(). r=ekr 2013-07-24 09:05:55 -04:00
transportlayerdtls.h
transportlayerice.cpp Bug 889615 - Add Granular logging to Mediapipeline. r=abr 2013-07-03 11:40:36 -07:00
transportlayerice.h
transportlayerlog.cpp Bug 889615 - Add Granular logging to Mediapipeline. r=abr 2013-07-03 11:40:36 -07:00
transportlayerlog.h
transportlayerloopback.cpp Bug 884061 - Part 3o: Use NS_DECL_THREADSAFE_ISUPPORTS in media/, r=abr 2013-07-18 21:23:32 -05:00
transportlayerloopback.h Bug 884061 - Part 3o: Use NS_DECL_THREADSAFE_ISUPPORTS in media/, r=abr 2013-07-18 21:23:32 -05:00
transportlayerprsock.cpp Bug 884061 - Part 3o: Use NS_DECL_THREADSAFE_ISUPPORTS in media/, r=abr 2013-07-18 21:23:32 -05:00
transportlayerprsock.h Bug 884061 - Part 3o: Use NS_DECL_THREADSAFE_ISUPPORTS in media/, r=abr 2013-07-18 21:23:32 -05:00

This is a generic media transport system for WebRTC.

The basic model is that you have a TransportFlow which contains a
series of TransportLayers, each of which gets an opportunity to
manipulate data up and down the stack (think SysV STREAMS or a
standard networking stack). You can also address individual
sublayers to manipulate them or to bypass reading and writing
at an upper layer; WebRTC uses this to implement DTLS-SRTP.


DATAFLOW MODEL
Unlike the existing nsSocket I/O system, this is a push rather
than a pull system. Clients of the interface do writes downward
with SendPacket() and receive notification of incoming packets
via callbacks registed via sigslot.h. It is the responsibility
of the bottom layer (or any other layer which needs to reference
external events) to arrange for that somehow; typically by
using nsITimer or the SocketTansportService.

This sort of push model is a much better fit for the demands
of WebRTC, expecially because ICE contexts span multiple
network transports.


THREADING MODEL
There are no thread locks. It is the responsibility of the caller to
arrange that any given TransportLayer/TransportFlow is only
manipulated in one thread at once. One good way to do this is to run
everything on the STS thread. Many of the existing layer implementations
(TransportLayerPrsock, TransportLayerIce, TransportLayerLoopback)
already run on STS so in those cases you must run on STS, though
you can do setup on the main thread and then activate them on the
STS.


EXISTING TRANSPORT LAYERS
The following transport layers are currently implemented:

* DTLS -- a wrapper around NSS's DTLS [RFC 6347] stack
* ICE  -- a wrapper around the nICEr ICE [RFC 5245] stack.
* Prsock -- a wrapper around NSPR sockets
* Loopback -- a loopback IO mechanism
* Logging -- a passthrough that just logs its data

The last three are primarily for debugging.