Provide mutable members of UrlRequestContext via pure-virtual interface

chrome/browser/profiles/profile_io_data.cc

Index: chrome/browser/profiles/profile_io_data.cc
diff --git a/chrome/browser/profiles/profile_io_data.cc b/chrome/browser/profiles/profile_io_data.cc
index 74f94d81938228a36127195cb3c02179c75ab86f..693ce18962b8449a78585695bf6025d45341127b 100644
--- a/chrome/browser/profiles/profile_io_data.cc
+++ b/chrome/browser/profiles/profile_io_data.cc
@@ -584,8 +584,8 @@ void ProfileIOData::LazyInitialize() const {
 void ProfileIOData::ApplyProfileParamsToContext(
     ChromeURLRequestContext* context) const {
   context->set_is_incognito(is_incognito());
-  context->set_accept_language(profile_params_->accept_language);
-  context->set_accept_charset(profile_params_->accept_charset);
+  context->OnAcceptLanguageChange(profile_params_->accept_language);

[erikwright (departed), 2012/09/25 21:06:38]

Is there actually any compelling reason for these to appear in profile_params_
now?

[pauljensen, 2012/09/26 14:08:19]

They come from the prefs so I believe they must be read on the UI thread but
they need to be put into the contexts which live on the IO thread and I believe
profile_params_ is used for moving this sort of initialization parameters from
the UI to IO thread.

+  context->OnDefaultCharsetChange(profile_params_->accept_charset);
   context->set_referrer_charset(profile_params_->referrer_charset);
   context->set_ssl_config_service(profile_params_->ssl_config_service);
 }