Always create URLRequestContextGetter in ChromotingHostContext.

Always create URLRequestContextGetter in ChromotingHostContext.

BUG=124728
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=133974

[Jamie, 2012-04-25 15:59:11]

lgtm

[Sergey Ulanov, 2012-04-25 18:04:31]

Currently ProxyConfigServiceLinux doesn't work on plugin threads and fix is
blocked is blocked by some changes in src/base
(http://codereview.chromium.org/10210008/ and
http://codereview.chromium.org/10213012/). I commented the Linux version of
ProxyConfigService creation. For now the Linux version will just use
ProxyConfigServiceDirect(). I'll fix that later once it is possible to use
ProxyConfigServiceLinux on plugin threads.

On 2012/04/25 15:59:11, Jamie wrote:
> lgtm

[commit-bot: I haz the power, 2012-04-25 18:04:51]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/sergeyu@chromium.org/10173009/12001

[commit-bot: I haz the power, 2012-04-25 18:38:16]

Try job failure for 10173009-12001 (retry) on linux_rel for step "compile"
(clobber build).
It's a second try, previously, step "compile" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_rel&...

[commit-bot: I haz the power, 2012-04-25 18:48:46]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/sergeyu@chromium.org/10173009/14003

[commit-bot: I haz the power, 2012-04-25 19:12:54]

Try job failure for 10173009-14003 (retry) on mac_rel for step "compile"
(clobber build).
It's a second try, previously, step "compile" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...

[commit-bot: I haz the power, 2012-04-25 19:18:15]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/sergeyu@chromium.org/10173009/12

[commit-bot: I haz the power, 2012-04-25 20:48:52]

Change committed as 133974

[pauljensen, 2012-11-06 18:48:12]

Are these issues resolved?  It looks like it.  I'm wondering if
base::OneShotTimer is safe to use now.

On 2012/04/25 18:04:31, sergeyu wrote:
> Currently ProxyConfigServiceLinux doesn't work on plugin threads and fix is
> blocked is blocked by some changes in src/base
> (http://codereview.chromium.org/10210008/ and
> http://codereview.chromium.org/10213012/). I commented the Linux version of
> ProxyConfigService creation. For now the Linux version will just use
> ProxyConfigServiceDirect(). I'll fix that later once it is possible to use
> ProxyConfigServiceLinux on plugin threads.
> 
> On 2012/04/25 15:59:11, Jamie wrote:
> > lgtm

[Sergey Ulanov, 2012-11-06 21:06:09]

On 2012/11/06 18:48:12, pauljensen wrote:
> Are these issues resolved?  It looks like it.  I'm wondering if
> base::OneShotTimer is safe to use now.

I fixed base::OneShotTimer to use base::ThreadTaskRunnerHandle, but currently
the host plugin doesn't set base::ThreadTaskRunnerHandle for the main plugin
thread. In other words OneShotTimer still doesn't work on the main thread in the
remoting plugin, but it should be easy to fix.


> 
> On 2012/04/25 18:04:31, sergeyu wrote:
> > Currently ProxyConfigServiceLinux doesn't work on plugin threads and fix is
> > blocked is blocked by some changes in src/base
> > (http://codereview.chromium.org/10210008/ and
> > http://codereview.chromium.org/10213012/). I commented the Linux version of
> > ProxyConfigService creation. For now the Linux version will just use
> > ProxyConfigServiceDirect(). I'll fix that later once it is possible to use
> > ProxyConfigServiceLinux on plugin threads.
> > 
> > On 2012/04/25 15:59:11, Jamie wrote:
> > > lgtm