[FileSystem] Add another copy-or-move validation hook for post-write.

chrome/browser/media_galleries/fileapi/supported_image_type_validator.h

Index: chrome/browser/media_galleries/fileapi/supported_image_type_validator.h
diff --git a/chrome/browser/media_galleries/fileapi/supported_image_type_validator.h b/chrome/browser/media_galleries/fileapi/supported_image_type_validator.h
index 8c655b5542065b2dd4e27e30a28210d937c8e351..2945b4a2ac499ad510d9a8dfc4e3c948d8e6a49b 100644
--- a/chrome/browser/media_galleries/fileapi/supported_image_type_validator.h
+++ b/chrome/browser/media_galleries/fileapi/supported_image_type_validator.h
@@ -13,6 +13,10 @@
 
 class ImageDecoder;
 
+namespace webkit_blob {
+class ShareableFileReference;
+}
+
 namespace chrome {
 
 class MediaFileValidatorFactory;
@@ -26,8 +30,12 @@ class SupportedImageTypeValidator : public fileapi::CopyOrMoveFileValidator {
   static bool SupportsFileType(const base::FilePath& path);
 
   virtual void StartValidation(
-      const fileapi::CopyOrMoveFileValidator::ResultCallback&
-          result_callback) OVERRIDE;
+      const ResultCallback& result_callback) OVERRIDE;
+
+  virtual void StartPostWriteValidation(
+      const base::FilePath& dest_platform_path,
+      scoped_refptr<webkit_blob::ShareableFileReference> file_ref,
+      const ResultCallback& result_callback) OVERRIDE;
 
  private:
   friend class MediaFileValidatorFactory;
@@ -39,6 +47,7 @@ class SupportedImageTypeValidator : public fileapi::CopyOrMoveFileValidator {
   base::FilePath path_;
   scoped_refptr<ImageDecoder> decoder_;
   fileapi::CopyOrMoveFileValidator::ResultCallback callback_;
+  fileapi::CopyOrMoveFileValidator::ResultCallback post_write_callback_;

[vandebo (ex-Chrome), 2013/07/10 15:52:46]

I'm pretty sure we can just use |callback_| for both stages.  We can reset it
when used and DCHECK that it is null before setting it.

[Greg Billock, 2013/07/11 22:54:35]

I agree we could, but I think this reads more straightforward.

[vandebo (ex-Chrome), 2013/07/12 15:08:15]

I'm not sure having two different members adds anything, but it does cost
space... not going to push any harder though.

   base::WeakPtrFactory<SupportedImageTypeValidator> weak_factory_;
 
   DISALLOW_COPY_AND_ASSIGN(SupportedImageTypeValidator);