Add FileSystemMountPointProvider::CreateFileReader() which returns appropriate Reader instance

webkit/chromeos/fileapi/cros_mount_point_provider.cc

Index: webkit/chromeos/fileapi/cros_mount_point_provider.cc
diff --git a/webkit/chromeos/fileapi/cros_mount_point_provider.cc b/webkit/chromeos/fileapi/cros_mount_point_provider.cc
index 74d0849e016188f217775afe5030b0dffa8920da..e73516f936567b8219ba28fcb435c243df5a5d01 100644
--- a/webkit/chromeos/fileapi/cros_mount_point_provider.cc
+++ b/webkit/chromeos/fileapi/cros_mount_point_provider.cc
@@ -18,6 +18,7 @@
 #include "third_party/WebKit/Source/WebKit/chromium/public/platform/WebString.h"
 #include "webkit/chromeos/fileapi/file_access_permissions.h"
 #include "webkit/chromeos/fileapi/remote_file_system_operation.h"
+#include "webkit/fileapi/file_system_file_reader.h"
 #include "webkit/fileapi/file_system_operation.h"
 #include "webkit/fileapi/file_system_util.h"
 #include "webkit/fileapi/native_file_util.h"
@@ -252,6 +253,17 @@ CrosMountPointProvider::CreateFileSystemOperation(
   return new fileapi::FileSystemOperation(file_proxy, context);
 }
 
+webkit_blob::FileReader* CrosMountPointProvider::CreateFileReader(
+    const GURL& url,
+    int64 offset,
+    base::MessageLoopProxy* file_proxy,

[zel, 2012/04/13 22:56:56]

are you guys planning to get rid of file_proxy business and go with IO blocking
thread pool instead?

+    fileapi::FileSystemContext* context) const {
+  // For now we return a generic Reader implementation which utilizes
+  // CreateSnapshotFile internally (i.e. will download everything first).
+  // TODO(satorux,zel): implement more efficient reader for remote cases.
+  return new fileapi::FileSystemFileReader(file_proxy, context, url, offset);
+}
+
 bool CrosMountPointProvider::GetVirtualPath(const FilePath& filesystem_path,
                                            FilePath* virtual_path) {
   for (MountPointMap::const_iterator iter = mount_point_map_.begin();