Replace AttachmentStore's StoreAttachments with UploadAttachments.

components/sync_driver/generic_change_processor.cc

 // Copyright 2014 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 "components/sync_driver/generic_change_processor.h"
 
 #include "base/location.h"
 #include "base/strings/string_number_conversions.h"
 #include "base/strings/utf_string_conversions.h"
 #include "components/sync_driver/sync_api_component_factory.h"
@@ skipping 67 matching lines @@
   sync_pb::EntitySpecifics password_holder;
   password_holder.mutable_password()->mutable_client_only_encrypted_data()->
       CopyFrom(read_node.GetPasswordSpecifics());
   return syncer::SyncData::CreateRemoteData(sync_id,
                                             password_holder,
                                             read_node.GetModificationTime(),
                                             attachment_ids,
                                             attachment_service_proxy);
 }
 
+const syncer::AttachmentId& AttachmentToAttachmentId(
+    const syncer::Attachment& attachment) {
+  return attachment.GetId();
+}
+
 }  // namespace
 
 GenericChangeProcessor::GenericChangeProcessor(
     DataTypeErrorHandler* error_handler,
     const base::WeakPtr<syncer::SyncableService>& local_service,
     const base::WeakPtr<syncer::SyncMergeResult>& merge_result,
     syncer::UserShare* user_share,
     SyncApiComponentFactory* sync_factory)
     : ChangeProcessor(error_handler),
       local_service_(local_service),
       merge_result_(merge_result),
       share_handle_(user_share),
       attachment_service_(
           sync_factory->CreateAttachmentService(*user_share, this)),
       attachment_service_weak_ptr_factory_(attachment_service_.get()),
       attachment_service_proxy_(
           base::MessageLoopProxy::current(),
-          attachment_service_weak_ptr_factory_.GetWeakPtr()) {
+          attachment_service_weak_ptr_factory_.GetWeakPtr()),
+      weak_ptr_factory_(this) {
   DCHECK(CalledOnValidThread());
   DCHECK(attachment_service_);
 }
 
 GenericChangeProcessor::~GenericChangeProcessor() {
   DCHECK(CalledOnValidThread());
 }
 
 void GenericChangeProcessor::ApplyChangesFromSyncModel(
     const syncer::BaseTransaction* trans,
@@ skipping 264 matching lines @@
           type, error_handler);
     }
   }
   if (IsActOnceDataType(type))
     node->Drop();
   else
     node->Tombstone();
   return syncer::SyncError();
 }
 
-// A callback invoked on completion of AttachmentService::StoreAttachment.
-void IgnoreStoreResult(const syncer::AttachmentService::StoreResult&) {
-  // TODO(maniscalco): Here is where we're going to update the in-directory
-  // entry to indicate that the attachments have been successfully stored on
-  // disk.  Why do we care?  Because we might crash after persisting the
-  // directory to disk, but before we have persisted its attachments, leaving us
-  // with danging attachment ids.  Having a flag that indicates we've stored the
-  // entry will allow us to detect and filter entries with dangling attachment
-  // ids (bug 368353).
-}
-
-void StoreAttachments(syncer::AttachmentService* attachment_service,
-                      const syncer::AttachmentList& attachments) {
-  DCHECK(attachment_service);
-  syncer::AttachmentService::StoreCallback ignore_store_result =
-      base::Bind(&IgnoreStoreResult);
-  attachment_service->StoreAttachments(attachments, ignore_store_result);
-}
-
 }  // namespace
 
 syncer::SyncError GenericChangeProcessor::ProcessSyncChanges(
     const tracked_objects::Location& from_here,
     const syncer::SyncChangeList& list_of_changes) {
   DCHECK(CalledOnValidThread());
 
   // Keep track of brand new attachments so we can persist them on this device
   // and upload them to the server.
   syncer::AttachmentList new_attachments;
@@ skipping 39 matching lines @@
               change.location().ToString(),
           type);
       error_handler()->OnSingleDataTypeUnrecoverableError(error);
       NOTREACHED();
       LOG(ERROR) << "Unset sync change.";
       return error;
     }
   }
 
   if (!new_attachments.empty()) {
-    StoreAttachments(attachment_service_.get(), new_attachments);
+    StoreAndUploadAttachments(new_attachments);
   }
 
   return syncer::SyncError();
 }
 
 // WARNING: this code is sensitive to compiler optimizations. Be careful
 // modifying any code around an OnSingleDataTypeUnrecoverableError call, else
 // the compiler attempts to merge it with other calls, losing useful information
 // in breakpad uploads.
 syncer::SyncError GenericChangeProcessor::HandleActionAdd(
@@ skipping 225 matching lines @@
 }
 
 void GenericChangeProcessor::StartImpl() {
 }
 
 syncer::UserShare* GenericChangeProcessor::share_handle() const {
   DCHECK(CalledOnValidThread());
   return share_handle_;
 }
 
+void GenericChangeProcessor::StoreAndUploadAttachments(
+    const syncer::AttachmentList& attachments) {
+  DCHECK(CalledOnValidThread());
+  attachment_service_->GetStore()->Write(
+      attachments,
+      base::Bind(&GenericChangeProcessor::WriteAttachmentsDone,
+                 weak_ptr_factory_.GetWeakPtr(),
+                 attachments));
+}
+
+void GenericChangeProcessor::WriteAttachmentsDone(
+    const syncer::AttachmentList& attachments,
+    const syncer::AttachmentStore::Result& result) {
+  DCHECK(CalledOnValidThread());
+  if (result != syncer::AttachmentStore::SUCCESS) {
+    // TODO(maniscalco): Deal with case where an error occurred (bug 361251).
+    return;
+  }
+
+  // TODO(maniscalco): Here is where we're going to update the in-directory
+  // entry to indicate that the attachments have been successfully stored on
+  // disk.  Why do we care?  Because we might crash after persisting the
+  // directory to disk, but before we have persisted its attachments, leaving us
+  // with danging attachment ids.  Having a flag that indicates we've stored the
+  // entry will allow us to detect and filter entries with dangling attachment
+  // ids (bug 368353).
+
+  // Begin uploading the attachments now that they are safe on disk.
+  syncer::AttachmentIdSet attachment_ids;
+  std::transform(attachments.begin(),
+                 attachments.end(),
+                 std::inserter(attachment_ids, attachment_ids.end()),
+                 AttachmentToAttachmentId);
+  attachment_service_->UploadAttachments(attachment_ids);
+}
+
 }  // namespace sync_driver