Change {Obfuscated|Local}FileSystemFileUtil non-Singleton to take an underlying *FileUtil.

webkit/fileapi/file_system_path_manager.h

Index: webkit/fileapi/file_system_path_manager.h
diff --git a/webkit/fileapi/file_system_path_manager.h b/webkit/fileapi/file_system_path_manager.h
index 5ac35612243fda6dc747868612951a159adf2bc7..1a60ade0190a36370d5337873a3e31c232528b8c 100644
--- a/webkit/fileapi/file_system_path_manager.h
+++ b/webkit/fileapi/file_system_path_manager.h
@@ -22,6 +22,7 @@ namespace fileapi {
 
 class ExternalFileSystemMountPointProvider;
 class FileSystemFileUtil;
+class LocalFileSystemFileUtil;
 class SandboxMountPointProvider;
 
 class FileSystemPathManager {
@@ -95,6 +96,7 @@ class FileSystemPathManager {
  private:
   const bool is_incognito_;
   const bool allow_file_access_from_files_;
+  scoped_ptr<LocalFileSystemFileUtil> local_file_util_;

[ericu, 2011/06/17 20:32:07]

This seems odd.  Why should a FileSystemPathManager own a FSFU subclass
directly?  Shouldn't it be the external_provider_ that takes care of this, just
as the SandboxMountPointProvider supplies the one for the sandbox?

[Dai Mikurube (NOT FULLTIME), 2011/06/23 08:13:32]

Agreed.  It's better for the FSFU instance in MountPointProvider.  Moved it to
CrosMountPointProvider.

But actually, GetFileSystemFileUtil() in FileSystemPathManager and
MountPointProvider looks like a little strange to me.  My thought is "Which
-FileUtil to be used" doesn't depend only on the GURL path.  What do you think?
(I think it'll be in another issue even if we decide to change it.)

   scoped_ptr<SandboxMountPointProvider> sandbox_provider_;
   scoped_ptr<ExternalFileSystemMountPointProvider> external_provider_;