Currently, there is the ResourceClient interface, which can be used to resouce load callbacks, and ResourceOwner, which adds Resource pointer management to ResourceClient. Some callers use ResourceClient directly, while others use ResourceOwner. There's no reason to have two different ways to interact with a Resource, so merge them.
Once they're merged, we can look at ways to improve the interaction around start-of-request. We currently start a resource load, then in a separate call add the ResourceClient to listen to any callbacks. Ideally that would be a single step.
Comment 1 by bugdroid1@chromium.org
, Dec 2 2017