Merge 208347 "Revert 208315 "Make use of InvalidationService""

Merge 208347 "Revert 208315 "Make use of InvalidationService""

> Revert 208315 "Make use of InvalidationService"
> 
> > Make use of InvalidationService
> > 
> > The InvalidationService was introduced r199520.  That commit added the
> > InvalidationService interface and several implementations of it, but
> > made no use of the new code.  This commit builds on that work.
> > 
> > Up until now, TICL invalidations were handled on the sync thread.  The
> > related objects were instantiated and owned by the SyncBackendHost and
> > SyncManager.  All requests to update the set of object registrations had
> > to be passed to the sync thread.  Components that wanted to receive
> > invalidations but were not part of sync had to route their communication
> > with the invalidations server through ProfileSyncService to get to the
> > sync thread.  Things were a bit different on Android, but the system
> > still tried to pretend that invalidations were owned by the sync thread.
> > 
> > The new InvalidationService implementation is a ProfileKeyedService that
> > is mostly independent from sync.  It still relies on sync to manage sign
> > in and fetch the appropriate auth tokens.  However, it's now much easier
> > for components outside of sync to communication with the invalidations
> > server.
> > 
> > The new system allows us to remove a lot of invalidations-related code
> > from the ProfileSyncService, SyncBackendHost and SyncManager.  Sync is
> > now just one of many clients of the InvalidationService.  The
> > SyncBackendHost is responsible for forwarding messages back and forth
> > between the InvalidationService and the sync thread.
> > 
> > TBR=sky,erg
> > BUG=124137
> > 
> > Review URL: https://chromiumcodereview.appspot.com/15580002
> 
> TBR=rlarocque@chromium.org
> 
> Review URL: https://codereview.chromium.org/17610004

TBR=rlarocque@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=208733

[rlarocque, 2013-06-26 18:08:30]

Committed patchset #1 manually as r208733.