Write a single API surface for mtransport

RESOLVED FIXED in Firefox 65

Status

()

enhancement
P2
normal
Rank:
15
RESOLVED FIXED
7 months ago
6 months ago

People

(Reporter: bwc, Assigned: bwc)

Tracking

(Blocks 1 bug)

60 Branch
mozilla65
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox65 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

7 months ago
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.
(Assignee)

Updated

7 months ago
Rank: 15
(Assignee)

Updated

7 months ago
Blocks: 1494311
Attachment #9012988 - Attachment description: Bug 1494301: (WIP) Single API for mtransport. → Bug 1494301: Single API for mtransport.

Comment 32

6 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/11819394462e
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in before you can comment on or make changes to this bug.