[CrOS MultiDevice] Refactor GcmDeviceInfo generation.
When a device registers to use the CryptAuth back-end, it sends a GcmDeviceInfo proto message. Before this CL, this was done from within ChromeCryptAuthService, which resides in //chrome. In order to share this code with the in-progress DeviceSync service, this CL refactors this code and moves it to a new location where it can be shared between both clients. Implementation is split between a pure-virtual GcmDeviceInfoProvider class living in //components/cryptauth and an implementation which has //chrome dependencies in //chrome/browser/chromeos/cryptauth. This separation is necessary so that the DeviceSync services, which resides in //chromeos, can utilize this class behind an interface. Bug: 824568, 752273 Change-Id: I0b5a4401809185cf3beef7e95cc1a68c369eaa79 Reviewed-on: https://chromium-review.googlesource.com/991234Reviewed-by:James Hawkins <jhawkins@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#547895}
Showing
Please register or sign in to comment