Closed
Bug 782434
Opened 13 years ago
Closed 12 years ago
Make ICE respond before start checks called
Categories
(Core :: WebRTC: Networking, defect, P2)
Core
WebRTC: Networking
Tracking
()
RESOLVED
DUPLICATE
of bug 886120
People
(Reporter: ekr, Assigned: ekr)
Details
(Whiteboard: [WebRTC], [blocking-webrtc-])
Currently, nICEr will only respond to checks after start checks is called. This means that there is a race condition if the other side starts checks too early.
|
||
Updated•13 years ago
|
Whiteboard: [WebRTC], [blocking-webrtc+]
|
||
Comment 1•12 years ago
|
||
Is this still true? If so, what needs to be done to resolve it, and who should work on it?
Flags: needinfo?(ekr)
|
Assignee | |
Comment 2•12 years ago
|
||
yes, it's still true.
The fix is to add a default responder that responds but doesn't have any callbacks. It's just kinda tricky since it involves messing around in nICEr and that code is unobvious to people who didn't work on it.
Flags: needinfo?(ekr)
|
|
||
Updated•12 years ago
|
Assignee: nobody → ekr
Priority: -- → P2
|
|
||
Comment 3•12 years ago
|
||
In some cases where there is a long latency in getting the answer to the offer. (5 sec plus)
Whiteboard: [WebRTC], [blocking-webrtc+] → [WebRTC], [blocking-webrtc-]
|
|
Assignee | |
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•