Open
Bug 1157887
Opened 10 years ago
Updated 3 years ago
Need tests for DataChannel expansion of number of channels
Categories
(Core :: WebRTC: Networking, defect, P4)
Core
WebRTC: Networking
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox40 | --- | affected |
| backlog | webrtc/webaudio+ |
People
(Reporter: jesup, Unassigned)
References
Details
We should add a test for DataChannels for forcing DataChannels to increase the number of channels. Also it should test pre-negotiated channels, and a pre-negotiated channel forcing the number of channels to increase.
I think we once had tests that bumped the number of channels above the old default (16); that seems to have been lost somewhere (long ago). The new limit is 256 (i.e. it'll renegotiate above 128 channels created by one side). You can check the channel id to loop creating channels until the ondatachannel gives a channel above 256 (and then pass a message over it). For pre-negotiated, create a channel < 256, verify it works (this is already there in CREATE_NEGOTIATED_CHANNEL), then create a channel >256 and verify it works.
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 35
Priority: -- → P3
Comment 1•8 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•