Open
Bug 1561671
Opened 6 years ago
Updated 2 years ago
Consider running stun address code on socket process
Categories
(Core :: WebRTC: Networking, defect, P2)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox69 | --- | affected |
People
(Reporter: dminor, Unassigned)
References
(Blocks 1 open bug)
Details
Sorry if I've missed something, but it looks like the StunAddrsRequest IPC calls are still going over to main. Is it possible for this to now run on the socket process?
Comment 1•6 years ago
|
||
Byron, thoughts (after you're back from PTO)?
Flags: needinfo?(docfaraday)
Priority: -- → P2
Comment 2•6 years ago
|
||
I think this should be possible, yes. However, we don't always run with the socket process, so we still need to be able to IPC this to the parent process. What this will probably end up looking like is moving this code from PeerConnectionMedia to MediaTransportHandlerSTS, which will use StunAddrsRequest if it is running on a content process, or call NrIceCtx::GetStunAddrs directly otherwise (ie; running on either the parent or the socket process).
Flags: needinfo?(docfaraday)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•