This simplifies the Mojo code a bit, and it makes it consistent with all other ResourceHandler methods, which always use ResourceController for resuming and cancellation, rather than returning a bool.
The conversion isn't too difficult, but will require tests for everything that calls the method and can see async results (ResourceLoader, InterceptingRH, DetachableRH, MimeSniffingRH, and Mojo test, too, if I switch that over to being able to allocate the buffer asychronously in the same CL - on the fence about that, may be better to split it off in another CL).
Comment 1 by mmenke@chromium.org
, Jan 31 2017