|
|
Created:
5 years, 3 months ago by the sun Modified:
5 years, 2 months ago CC:
webrtc-reviews_webrtc.org, interface-changes_webrtc.org, rwolff_gocast.it, yujie_mao (webrtc), tterriberry_mozilla.com, qiang.lu, niklas.enbom, kwiberg-webrtc Base URL:
https://chromium.googlesource.com/external/webrtc.git@master Target Ref:
refs/pending/heads/master Project:
webrtc Visibility:
Public. |
DescriptionSimplify handling of options in WebRtcVoiceMediaEngine.
Also removes unnecessary typedef ChannelList.
BUG=webrtc:4690
Committed: https://crrev.com/63b345441a995665c1cdd0329b65f895675874ff
Cr-Commit-Position: refs/heads/master@{#10107}
Patch Set 1 #
Total comments: 5
Patch Set 2 : fix+rebase #Patch Set 3 : comment #Patch Set 4 : rebase #Patch Set 5 : rebase #Patch Set 6 : rebase #Messages
Total messages: 22 (6 generated)
solenberg@webrtc.org changed reviewers: + andrew@webrtc.org
solenberg@webrtc.org changed reviewers: + pbos@webrtc.org
https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... File talk/media/webrtc/webrtcvoiceengine.cc (right): https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... talk/media/webrtc/webrtcvoiceengine.cc:1222: auto i = std::find(channels_.begin(), channels_.end(), channel); s/i/it/ https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... talk/media/webrtc/webrtcvoiceengine.cc:2053: engine()->ApplyOptions(engine()->GetOptions()); Why is this not a no-op?
https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... File talk/media/webrtc/webrtcvoiceengine.cc (right): https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... talk/media/webrtc/webrtcvoiceengine.cc:1222: auto i = std::find(channels_.begin(), channels_.end(), channel); On 2015/09/23 13:41:34, pbos-webrtc wrote: > s/i/it/ Done. https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... talk/media/webrtc/webrtcvoiceengine.cc:2053: engine()->ApplyOptions(engine()->GetOptions()); On 2015/09/23 13:41:34, pbos-webrtc wrote: > Why is this not a no-op? Because the engine options_ can be different from the channel options_. Yes, it is confusing. This CL makes it a little less confusing.
https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... File talk/media/webrtc/webrtcvoiceengine.cc (right): https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... talk/media/webrtc/webrtcvoiceengine.cc:2053: engine()->ApplyOptions(engine()->GetOptions()); On 2015/09/23 15:11:28, the sun wrote: > On 2015/09/23 13:41:34, pbos-webrtc wrote: > > Why is this not a no-op? > > Because the engine options_ can be different from the channel options_. Yes, it > is confusing. This CL makes it a little less confusing. But you're applying engine's GetOptions to engine? Or are there separate engine()s? Put a comment here?
On 2015/09/23 15:13:14, pbos-webrtc wrote: > https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... > File talk/media/webrtc/webrtcvoiceengine.cc (right): > > https://codereview.webrtc.org/1364753002/diff/1/talk/media/webrtc/webrtcvoice... > talk/media/webrtc/webrtcvoiceengine.cc:2053: > engine()->ApplyOptions(engine()->GetOptions()); > On 2015/09/23 15:11:28, the sun wrote: > > On 2015/09/23 13:41:34, pbos-webrtc wrote: > > > Why is this not a no-op? > > > > Because the engine options_ can be different from the channel options_. Yes, > it > > is confusing. This CL makes it a little less confusing. > > But you're applying engine's GetOptions to engine? Or are there separate > engine()s? Put a comment here? Good pint. Point.
Andrew, can you please check the sanity of this change? Is the logic for resetting the options to the engine defaults really required?
andrew@webrtc.org changed reviewers: + pthatcher@webrtc.org
On 2015/09/23 15:33:36, the sun wrote: > Andrew, can you please check the sanity of this change? Is the logic for > resetting the options to the engine defaults really required? I _think_ this was needed to support the Talk plugin's configuration file. It shouldn't be needed any longer. Peter T. added this code, he might recall better.
On 2015/09/23 17:51:12, Andrew MacDonald wrote: > On 2015/09/23 15:33:36, the sun wrote: > > Andrew, can you please check the sanity of this change? Is the logic for > > resetting the options to the engine defaults really required? > > I _think_ this was needed to support the Talk plugin's configuration file. It > shouldn't be needed any longer. > > Peter T. added this code, he might recall better. This looks like a good simplification. I probably should have done it this way back when I wrote the code. Not sure why I made it so confusing. Sorry about that!
On 2015/09/23 19:54:06, pthatcher1 wrote: > On 2015/09/23 17:51:12, Andrew MacDonald wrote: > > On 2015/09/23 15:33:36, the sun wrote: > > > Andrew, can you please check the sanity of this change? Is the logic for > > > resetting the options to the engine defaults really required? > > > > I _think_ this was needed to support the Talk plugin's configuration file. It > > shouldn't be needed any longer. > > > > Peter T. added this code, he might recall better. > > This looks like a good simplification. I probably should have done it this way > back when I wrote the code. Not sure why I made it so confusing. Sorry about > that! Question is: do we really need to care about resetting the state once we stop sending? New options will be latched in when either a new channel is created, or sending is started again.
On 2015/09/24 07:57:37, the sun wrote: > Question is: do we really need to care about resetting the state once we stop > sending? > > New options will be latched in when either a new channel is created, or sending > is started again. I think what you have is good. It's reasonable for the client to provide the settings whenever they open a new channel. As I mentioned, I think this was just to manage the case of the Talk plugin having a default settings file.
So, provided you are ok with this, would you mind stamping it?
On 2015/09/28 10:36:11, the sun wrote: > So, provided you are ok with this, would you mind stamping it? Ah, lgtm. But I'm not actually a talk/* OWNER. pthatcher will have to approve.
lgtm
solenberg@webrtc.org changed reviewers: - pbos@webrtc.org
The CQ bit was checked by solenberg@webrtc.org
The patchset sent to the CQ was uploaded after l-g-t-m from pthatcher@webrtc.org, andrew@webrtc.org Link to the patchset: https://codereview.webrtc.org/1364753002/#ps100001 (title: "rebase")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1364753002/100001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1364753002/100001
Message was sent while issue was closed.
Committed patchset #6 (id:100001)
Message was sent while issue was closed.
Patchset 6 (id:??) landed as https://crrev.com/63b345441a995665c1cdd0329b65f895675874ff Cr-Commit-Position: refs/heads/master@{#10107} |