[Sync] - Implement isolated model association.

chrome/browser/sync/glue/data_type_manager.h

Index: chrome/browser/sync/glue/data_type_manager.h
diff --git a/chrome/browser/sync/glue/data_type_manager.h b/chrome/browser/sync/glue/data_type_manager.h
index 7dc7f15402e6bc63778538bdea5068ad8f2413f7..87f7f00df20eca02ebe882dc1f352581b0266218 100644
--- a/chrome/browser/sync/glue/data_type_manager.h
+++ b/chrome/browser/sync/glue/data_type_manager.h
@@ -60,11 +60,21 @@ class DataTypeManager {
                     TypeSet requested_types);
     ConfigureResult(ConfigureStatus status,
                     TypeSet requested_types,
-                    const std::list<SyncError>& errors);
+                    const std::list<SyncError>& failed_data_types,
+                    syncable::ModelTypeSet waiting_to_start);
     ~ConfigureResult();
     ConfigureStatus status;
     TypeSet requested_types;
-    std::list<SyncError> errors;
+
+    // These types encountered a failure in association.
+    std::list<SyncError> failed_data_types;
+
+    // These types are waiting to start associating. Since we have
+    // waited long enough we have exited out of the configure cycle.
+    // However these types could still be loading on the backend.
+    // However they will not start associating unless we are in a configure
+    // cycle.

[tim (not reviewing), 2012/05/21 23:18:57]

Wording is a bit unclear, perhaps "List of types that failed to start
association within our allotted time period (see kAssociationDeadline [or
whatever]).  We move forward here and allow these types to continue loading, but
association will not start until another configure cycle begins [what kicks this
off]?

[lipalani1, 2012/05/22 01:23:58]

Done.

+    syncable::ModelTypeSet waiting_to_start;
   };
 
   virtual ~DataTypeManager() {}