Implement a shim to allow existing feature components to run against the Helium 1.0 sync API |
|||
Issue descriptionAllow the messaging oriented feature-specific components that we have now, to run unmodified over the new Helium 1.0 sync API, by implementing a simple message-queue based syncable-object shim. We may skip this step if migrating the features directly to the new system proves to be less effort.
,
Nov 15 2016
We believe we can migrate Features directly to the Sync layer once we have that up and running.
,
Dec 9 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by w...@chromium.org
, Aug 9 2016