Add BrowserThread::PostTaskOnIOThread

Add BrowserThread::PostTaskOnIOThread

BUG=None
TEST=None

[piman, 2011-12-13 00:47:21]

Review at http://codereview.chromium.org/8921017/ suggested it could be useful,
but I wanted to limit scope and keep this change separate.
(This CL is based on top of 8921017)

[darin (slow to review), 2011-12-13 00:51:35]

http://codereview.chromium.org/8917028/diff/1/content/browser/renderer_host/r...
File content/browser/renderer_host/render_widget_host_view_win.cc (right):

http://codereview.chromium.org/8917028/diff/1/content/browser/renderer_host/r...
content/browser/renderer_host/render_widget_host_view_win.cc:551:
BrowserThread::PostTaskOnIOThread(
given how small this change is, maybe the PostTaskOn{Foo}Thread idea is not so
worth it?  sorry for the noise.

[piman, 2011-12-13 00:54:06]

On Mon, Dec 12, 2011 at 4:51 PM, <darin@chromium.org> wrote:

>
> http://codereview.chromium.**org/8917028/diff/1/content/**
>
browser/renderer_host/render_**widget_host_view_win.cc<http://codereview.chromium.org/8917028/diff/1/content/browser/renderer_host/render_widget_host_view_win.cc>
> File content/browser/renderer_host/**render_widget_host_view_win.cc
> (right):
>
> http://codereview.chromium.**org/8917028/diff/1/content/**
>
browser/renderer_host/render_**widget_host_view_win.cc#**newcode551<http://codereview.chromium.org/8917028/diff/1/content/browser/renderer_host/render_widget_host_view_win.cc#newcode551>
> content/browser/renderer_host/**render_widget_host_view_win.**cc:551:
> BrowserThread::**PostTaskOnIOThread(
> given how small this change is, maybe the PostTaskOn{Foo}Thread idea is
> not so worth it?  sorry for the noise.
>

TBH, I didn't look for all uses, just the ones in this file that I was
touching. It may help readability in many files. I'm open either way.

Antoine


>
>
http://codereview.chromium.**org/8917028/<http://codereview.chromium.org/8917...
>

[jam, 2011-12-13 11:55:58]

I think it's better not to add this, because it saves a small amount of code
that people are already familiar with. we shouldn't treat specific threads
differently in BrowserThread's API