Remove the restriction that ChromeURLRequestContextGetter needs to be release...

Cleanup some callers now that the restriction that ChromeURLRequestContextGetter be released from the IO thread is gone.

This was an anoyance for consumers of URLRequestContextGetter, as they would play tricks doing manual AddRef/Release.

The actual removal of this policy happened in: r32129.

BUG=None
Test=Existing tests don't crash/leak.

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

[darin (slow to review), 2009-10-23 17:54:23]

LGTM!

http://codereview.chromium.org/332006/diff/2004/2006
File chrome/browser/sync/glue/http_bridge.cc (right):

http://codereview.chromium.org/332006/diff/2004/2006#newcode33
Line 33: if (MessageLoop::current() != io_loop_) {
nit: consider joining these expressions with &&

[eroman, 2009-11-19 04:21:58]

Finally got around to committing this.

Removed the chrome_url_request_context.{cc|h} files from this change, since
r32129 already added the DeleteOnIOThread trait to URLRequestContextGetter.

[darin (slow to review), 2009-11-19 07:26:40]

OK

On Wed, Nov 18, 2009 at 8:21 PM, <eroman@chromium.org> wrote:

> Finally got around to committing this.
>
> Removed the chrome_url_request_context.{cc|h} files from this change, since
> r32129 already added the DeleteOnIOThread trait to URLRequestContextGetter.
>
> http://codereview.chromium.org/332006
>