diff options
| author | ericu@google.com <ericu@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-24 00:49:40 +0000 |
|---|---|---|
| committer | ericu@google.com <ericu@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-24 00:49:40 +0000 |
| commit | 073a04f0599beb27670d8a6738fcbbc22fa97bcf (patch) | |
| tree | d7393b3cd3463dbfaf4bbdc02fdd0a4de0c83995 /webkit/fileapi/file_system_usage_tracker.h | |
| parent | 6bcd5f36cd94649887eff0c87df4f4496001984a (diff) | |
| download | chromium_src-073a04f0599beb27670d8a6738fcbbc22fa97bcf.zip chromium_src-073a04f0599beb27670d8a6738fcbbc22fa97bcf.tar.gz chromium_src-073a04f0599beb27670d8a6738fcbbc22fa97bcf.tar.bz2 | |
Stop returning the true root path of each filesystem from openFileSystem.
Instead, return the FileSystem URI of the root. This will make it easier
to swap in different filesystem implementations.
BUG=71635
TEST=Just a couple in FileSystemUtilTests, but a bunch of existing ones [this doesn't add much new functionality].
Review URL: http://codereview.chromium.org/6603034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@79228 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/fileapi/file_system_usage_tracker.h')
| -rw-r--r-- | webkit/fileapi/file_system_usage_tracker.h | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/webkit/fileapi/file_system_usage_tracker.h b/webkit/fileapi/file_system_usage_tracker.h index 10a5177..af292a1 100644 --- a/webkit/fileapi/file_system_usage_tracker.h +++ b/webkit/fileapi/file_system_usage_tracker.h @@ -24,11 +24,10 @@ class MessageLoopProxy; namespace fileapi { -// Owned by the SandboxedFileSystemContext, which is a per-profile -// instance, and has the same lifetime as the SandboxedFileSystemContext. -// It's going to be created and destroyed on the IO thread in chrome. -// (The destruction on the same thread where it is created was guaranteed -// by its owner, SandboxedFileSystemContext.) +// Owned by the FileSystemContext, which is a per-profile instance, and has the +// same lifetime as the FileSystemContext. It's going to be created and +// destroyed on the IO thread in chrome. (The destruction on the same thread +// where it is created was guaranteed by its owner, FileSystemContext.) class FileSystemUsageTracker { public: FileSystemUsageTracker( |