********** Chromium Blob hacking

webkit/fileapi/webfilewriter_base.cc

 // Copyright (c) 2012 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 "webkit/fileapi/webfilewriter_base.h"
 
 #include "base/logging.h"
 #include "third_party/WebKit/Source/Platform/chromium/public/WebURL.h"
 #include "third_party/WebKit/Source/WebKit/chromium/public/WebFileError.h"
 #include "third_party/WebKit/Source/WebKit/chromium/public/WebFileWriterClient.h"
@@ skipping 14 matching lines @@
 
 void WebFileWriterBase::truncate(long long length) {
   DCHECK(kOperationNone == operation_);
   DCHECK(kCancelNotInProgress == cancel_state_);
   operation_ = kOperationTruncate;
   DoTruncate(path_, length);
 }
 
 void WebFileWriterBase::write(
       long long position,
-      const WebKit::WebURL& blob_url) {
+      const WebKit::WebString& blob_uuid) {
   DCHECK(kOperationNone == operation_);
   DCHECK(kCancelNotInProgress == cancel_state_);
   operation_ = kOperationWrite;
-  DoWrite(path_, blob_url, position);
+  DoWrite(path_, blob_uuid.utf8(), position);
 }
 
 // When we cancel a write/truncate, we always get back the result of the write
 // before the result of the cancel, no matter what happens.
 // So we'll get back either
 //   success [of the write/truncate, in a DidWrite(XXX, true)/DidSucceed() call]
 //     followed by failure [of the cancel]; or
 //   failure [of the write, either from cancel or other reasons] followed by
 //     the result of the cancel.
 // In the write case, there could also be queued up non-terminal DidWrite calls
@@ skipping 88 matching lines @@
 
 void WebFileWriterBase::FinishCancel() {
   DCHECK(kCancelReceivedWriteResponse == cancel_state_);
   DCHECK(kOperationNone != operation_);
   cancel_state_ = kCancelNotInProgress;
   operation_ = kOperationNone;
   client_->didFail(WebKit::WebFileErrorAbort);
 }
 
 }  // namespace fileapi