Add initial code to do filename munging in the FileSystem....

webkit/fileapi/obfuscated_file_util.h

+// Copyright (c) 2011 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef WEBKIT_FILEAPI_OBFUSCATED_FILE_UTIL_H_
+#define WEBKIT_FILEAPI_OBFUSCATED_FILE_UTIL_H_
+
+#include "base/file_path.h"
+#include "base/platform_file.h"
+
+namespace base {
+class Time;  // For TouchFile TODO remove comment when it's in.
+}
+
+namespace obfuscated_file_util {

[michaeln, 2011/02/11 00:03:34]

i don't think we generally use namespaces for this type of scoping, i think
these should all be in the fileapi namespace.

[ericu, 2011/02/11 01:57:47]

This matches base::file_util.  If I dump this all into the fileapi namespace, we
end up with file_util::CreateOrOpen vs. either just bare calls to CreateOrOpen
from inside fileapi, which might be confusing, or fully-qualified calls to
fileapi::CreateOrOpen, which isn't obviously something that obfuscates.

However, I think the cleaner solution is to go with something like what Dai
wrote up: we always access the obfuscated calls through an object of some sort,
and we make an object with similar interface to call out to file_util, so we get
obvious qualification on every call.  How does that sound?

+
+using base::PlatformFile;
+using base::PlatformFileError;
+
+PlatformFile CreateOrOpen(
+    const FilePath& root_path,
+    const FilePath& virtual_path,
+    int file_flags,
+    bool *created,
+    PlatformFileError* error);
+void CreateDirectory(
+    const FilePath& root_path,
+    const FilePath& virtual_path,
+    bool exclusive_,
+    PlatformFileError* error);
+}
+
+#endif  // WEBKIT_FILEAPI_OBFUSCATED_FILE_UTIL_H_