Closed Bug 907339 Opened 11 years ago Closed 10 years ago

Networking support to allow multiple audio and/or multiple video streams in PeerConnection

Categories

(Core :: WebRTC: Networking, defect, P1)

x86_64
Windows 7
defect

Tracking

()

RESOLVED DUPLICATE of bug 1095218
mozilla35

People

(Reporter: mreavy, Assigned: bwc)

References

(Blocks 1 open bug)

Details

(Whiteboard: [meta])

Follow on to Bug 784517, which is for the signaling piece to support multiple A/V flows. This is the networking piece to support multiple A/V flows.
This work would start after Jan 10 (after Bug 786234 is finished) and last approximately 12 weeks. This will likely turn into a meta bug, but I'd like to target this work for mid April (circa Gecko 32) initially, and we'll do lots more refinement as we get closer to this date.
Assignee: nobody → docfaraday
It'd be good to break this bug down into smaller bugs.
Priority: -- → P1
Whiteboard: [meta]
Target Milestone: --- → mozilla33
Flags: needinfo?(docfaraday)
asking Byron for breakdown into smaller parts and estimation, because he is working in this area already.
My biggest question is going to be what is considered under the umbrella of signalling support, since the two need to integrate. Once we remove some hard-coding of stuff (all entirely outside of things like ICE, RTP, etc), my suspicion is that it will not be much work. The best way to get you an estimate, I think, is to just try making it configurable (with defaults of what is hard-coded now), and try exercising this configurability in a unit test. This could be done independently of work on the JSEP side of things, I think.
Target Milestone: mozilla33 → mozilla34
Target Milestone: mozilla34 → mozilla35
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(docfaraday)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.