Bluetooth Mojo Service |
|||||
Issue descriptionFeature description: Design and implement a Bluetooth mojo based service. This can either be part of the device service or a separate service, depending on the design we go with. This service will serve as a replacement to calling directly into //device/bluetooth. The service will work cross-process and should be used by Ash and Chrome for any Bluetooth related operations. The interface initially provided will be the minimal set required by the UI surfaces in Chrome. Over time we can migrate more features to it. Eng owner: rkc@ Product owner: omrilio@ Design doc: <TBD>
,
Apr 9 2018
Isn't there a design doc for this? http://go/bt-mojo-service
,
Apr 9 2018
ARC++ will eventually use it as we flesh out the interfaces. I didn't want to link the existing design doc because it will need major rework and another re-review by chrome-design-docs. We may just start another doc referencing the older one.
,
Jul 11
,
Jul 11
If possible the service should run in the ash process under multiprocess ash ("mash").
,
Jul 11
In order to host this in Ash, we would have to replace all DBus access to bluetooth processes in src/chrome with calls to the new service, which might be challenging (and will certainly be more work than just replacing the Ash calls). We have the same problem with Networking, which is why I expect to host the network config service in the Chrome process, at least for the near term. That said, since we don't really have an existing model layer for Bluetooth, maybe we do want to replace all calls to DBus services with calls into the new API, in which case this could live in Ash.
,
Aug 21
,
Aug 21
,
Aug 21
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by snanda@chromium.org
, Apr 9 2018