[Blobs] Make task runner used by BlobBytesProvider more explicit.
Rather than just documenting that the class should be bound to a mojo pipe on a different thread than the main/worker threads, explicitly make the API such that it creates its own task runner to bind on. That same task runner is then also passed on to BlobBytesStreamer, to replace its usage of SequencedTaskRunnerHandle::Get(). Bug: 786332 Change-Id: Ic2e38a53514bc612ffaf579c3eb1bc4a88b29efe Reviewed-on: https://chromium-review.googlesource.com/976098Reviewed-by:Hajime Hoshi <hajimehoshi@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#545863}
Showing
Please register or sign in to comment