Closed Bug 1494301 Opened 6 years ago Closed 6 years ago

Write a single API surface for mtransport

Categories

(Core :: WebRTC: Networking, enhancement, P2)

60 Branch
enhancement

Tracking

()

RESOLVED FIXED
mozilla65
Tracking Status
firefox65 --- fixed

People

(Reporter: bwc, Assigned: bwc)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

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.
Rank: 15
Blocks: 1494311
Attachment #9012988 - Attachment description: Bug 1494301: (WIP) Single API for mtransport. → Bug 1494301: Single API for mtransport.
https://hg.mozilla.org/mozilla-central/rev/11819394462e
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: