Right now, the mtransport API is inconsistently encapsulated; PeerConnectionMedia wraps some functionality, but the MediaPipeline code uses TransportLayer/TransportFlow directly. We should have a single class that exposes the API we need, and no other code should use any of the mtransport classes (except some of the threading utility stuff maybe). This will get us closer to being able to move mtransport into a separate process.
Attachment #9012988 - Attachment description: Bug 1494301: (WIP) Single API for mtransport. → Bug 1494301: Single API for mtransport.
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/11819394462e Single API for mtransport. r=mjf
You need to log in before you can comment on or make changes to this bug.