[Sync] Refactor non-frontend DTC to handle new API properly.

chrome/browser/sync/glue/shared_change_processor_ref.cc

Index: chrome/browser/sync/glue/shared_change_processor_ref.cc
diff --git a/chrome/browser/sync/glue/shared_change_processor_ref.cc b/chrome/browser/sync/glue/shared_change_processor_ref.cc
new file mode 100644
index 0000000000000000000000000000000000000000..630a91616e60f240cfa0f1a20c1f5fd05f128508
--- /dev/null
+++ b/chrome/browser/sync/glue/shared_change_processor_ref.cc
@@ -0,0 +1,27 @@
+// Copyright (c) 2011 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "chrome/browser/sync/glue/shared_change_processor_ref.h"
+
+namespace browser_sync {
+
+SharedChangeProcessorRef::SharedChangeProcessorRef(
+    SharedChangeProcessor* change_processor)
+    : change_processor_(change_processor) {
+}
+
+SharedChangeProcessorRef::~SharedChangeProcessorRef() {}
+
+SyncError SharedChangeProcessorRef::ProcessSyncChanges(
+    const tracked_objects::Location& from_here,
+    const SyncChangeList& change_list) {
+  if (change_processor_.get()) {
+    return change_processor_->ProcessSyncChanges(from_here, change_list);

[akalin, 2011/10/07 20:51:16]

change_processor_ should be valid at construction-time, right?  So I think we
don't need the check.

[Nicolas Zea, 2011/10/07 22:05:52]

Done.

+  } else {
+    return SyncError(FROM_HERE, "Change processor not set yet.",
+                     syncable::UNSPECIFIED);
+  }
+}
+
+}  // namespace browser_sync