Make MountPointProvider pluggable from outside webkit/fileapi

Currently we have some layering leakages under webkit/ because
we have several FS modules (e.g. media modules) that
should not be known by WebKit/FileAPI (or content) layer.

Also some module implementors are forced to add extra glue interfaces
just to across layering boundaries from webkit.

This patch changes to:
- Add CanHandleType method to each MountPointProvider
- Make FileSystemContext's ctor take additional MountPointProviders and
  MountPoints, so that FS module implementors can implement their own
  provider outside webkit/ and plug it into FileAPI layer.

This is the 1st cut of a couple of planned changes.

Brief change plan (internal): https://docs.google.com/a/google.com/document/d/1XEtX0OO_RIA_c0KuKvd9yqK5l3XtsTulwXs3c-mAQ1o/view

BUG=175936
TEST=content_unittests:.*File.*
TEST=content_unittests:.*MountPointProvider.*

Review URL: https://codereview.chromium.org/14096022

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@194747 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 4 insertions, 0 deletions

diff --git a/webkit/fileapi/file_system_util.cc b/webkit/fileapi/file_system_util.cc
index 468abcf..3918ce0 100644
--- a/webkit/fileapi/file_system_util.cc
+++ b/webkit/fileapi/file_system_util.cc
@@ -241,6 +241,10 @@ std::string GetFileSystemTypeString(FileSystemType type) {
       return "Syncable";
     case kFileSystemTypeNativeForPlatformApp:
       return "NativeForPlatformApp";
+    case kFileSystemInternalTypeEnumStart:
+    case kFileSystemInternalTypeEnumEnd:
+      NOTREACHED();
+      // Fall through.
     case kFileSystemTypeUnknown:
       return "Unknown";
   }