We've decided that ModelTypeService isn't actually a great name because it's not obvious how derived classes should be named. For example, the DeviceInfo implementation is named DeviceInfoService, but this doesn't indicate at all its relationship to sync.
After some discussion, the team things that ModelTypeSyncBridge would be a more descriptive name. The word "bridge" is less overloaded than "service", is more descriptive (it is the bridge between the model type and sync), and lends itself to descriptive names of derived classes: DeviceInfoSyncBridge, etc.
Comment 1 by bugdroid1@chromium.org
, Oct 28 2016