[Tango->FCM] Part 1. Ditch the objectId from the new FCM-based architecture.
ObjectId is the representation of the subscription topic from the outdated Tango protocol. It's not relevant to the new architecture, since subscription is represented by topic name (in case of sync topic name is for example "BOOKMARKS" or "PASSWORDS"). After this CL all code related to the FCMInvalidationService won't use the ObjectId. But in some places the term Id still used. This is the subject for follow up refactoring. Bug: 878446, 801985 Change-Id: Idcf5bb464fff8976b319bd4721bdca2e3be77751 Reviewed-on: https://chromium-review.googlesource.com/1194032 Commit-Queue: Tatiana Gornak <melandory@chromium.org> Reviewed-by:Pavel Yatsuk <pavely@chromium.org> Cr-Commit-Position: refs/heads/master@{#587904}
Showing
This diff is collapsed.
Please register or sign in to comment