service-worker: Directly use the thread's TaskRunner instead of WorkerThreadTaskRunner.

service-worker: Directly use the thread's TaskRunner instead of WorkerThreadTaskRunner.

BUG=none
R=kinuko@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/1e811020d3a5717fbbf3d85f0b596fc28c99f178

[sadrul, 2015-02-04 18:03:37]

sadrul@chromium.org changed reviewers:
+ kinuko@chromium.org

[kinuko, 2015-02-05 02:58:54]

I'm a bit worried that we're making worker code more and more tightly tied onto
a single thread (it could make it difficult for background workers to run on,
say, thread pool), but the current code is not doing anything better... so LGTM.
 (I'll look into your doc)

[sadrul, 2015-02-05 04:14:01]

On 2015/02/05 02:58:54, kinuko wrote:
> I'm a bit worried that we're making worker code more and more tightly tied
onto
> a single thread (it could make it difficult for background workers to run on,
> say, thread pool), but the current code is not doing anything better... so
LGTM.
>  (I'll look into your doc)

Thanks!

WorkerThreadTaskRunner looks like something that can be removed without breaking
too many things, and without making life difficult for future changes. I am
trying to reduce its usage and see if it would be possible to remove it
entirely. Hopefully for thread-pool, we would have to change how we get a handle
to the task-runner (i.e. use something other than
base::ThreadTaskRunnerHandle::Get()), but not too many other things (in these
particular areas of code).

[commit-bot: I haz the power, 2015-02-05 16:41:21]

Patchset 1 (id:??) landed as
https://crrev.com/1e811020d3a5717fbbf3d85f0b596fc28c99f178
Cr-Commit-Position: refs/heads/master@{#314826}

[sadrul, 2015-02-05 16:41:32]

Committed patchset #1 (id:1) manually as
1e811020d3a5717fbbf3d85f0b596fc28c99f178 (presubmit successful).