As part of the transformation of //device into the Device Service, we need to servicify //device/media_transfer_protocol. From a quick inspection, this looks relatively straightforward. Here is my high-level analysis:
- The code is used by //chrome, //chrome/browser/chromeos, //components (entirely browser process clients).
- It looks like it's used on at least Linux and ChromeOS.
- The only public interface of the code is media_transfer_protocol_manager.h.
- Almost all of the methods of that class are already asynchronous, i.e., they take in a callback that gets invoked with the return value. These methods can likely be converted to Mojo in a straightforward way.
- It looks like there is some amount of synchronous methods exposed by that class as well -- I saw at least one synchronous accessor. We'll need to examine how to move those interactions to asynchronous.
Comment 1 by ke...@intel.com
, Nov 3 2017