Remove storage context accessors from ResourceContext.

content/public/browser/storage_partition.h

 // Copyright (c) 2012 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 CONTENT_PUBLIC_BROWSER_STORAGE_PARTITION_H_
 #define CONTENT_PUBLIC_BROWSER_STORAGE_PARTITION_H_
 
+#include <string>
+
 #include "base/basictypes.h"
 
 namespace appcache {
 class AppCacheService;
 }
 
 namespace fileapi {
 class FileSystemContext;
 }
 
@@ skipping 12 matching lines @@
 class DOMStorageContext;
 
 // Defines what persistent state a child process can access.
 //
 // The StoragePartition defines the view each child process has of the
 // persistent state inside the BrowserContext. This is used to implement
 // isolated storage where a renderer with isolated storage cannot see
 // the cookies, localStorage, etc., that normal web renderers have access to.
 class StoragePartition {
  public:
+  // Returns the partition id for this StoragePartition.
+  //
+  // This value should be used to compare whether two StoragePartition objects
+  // are equivalent. On the IO thread, this can be particularly useful because
+  // StoragePartition objects themselves are only meant for use on the UI
+  // thread.

[michaeln, 2012/08/30 21:48:45]

I'm thinking that we could make this class thread safe refcounted and establish
relationships needed to glue things together on the IO thread roughly as
follows...

Each RenderProcessHost and WorkerProcessHost that's bound to a particular
partition would hold a reference to this object. The RenderProcessHost's
internal RenderWidgetHelper (helper that spans the IO and UI thread) would
actually hold that ref on behalf of the RenderProcessHost.

When it comes time to spin up a new WorkerProcessHost on the IO thread on behalf
of a particular renderer, we can navigate to the StoragePartition to be used via
RenderWidgetHelper::FromProcessHostID(renderer_id)->GetStoragePartition()). It's
data members are then used to initialize various message filters and such for
that process host.

In that world, the 'id' attribute wouldn't really be needed, ptr value
comparisons would be preferred.

+  virtual const std::string& GetId() = 0;
+
   virtual quota::QuotaManager* GetQuotaManager() = 0;
   virtual appcache::AppCacheService* GetAppCacheService() = 0;
   virtual fileapi::FileSystemContext* GetFileSystemContext() = 0;
   virtual webkit_database::DatabaseTracker* GetDatabaseTracker() = 0;
   virtual DOMStorageContext* GetDOMStorageContext() = 0;
   virtual IndexedDBContext* GetIndexedDBContext() = 0;
 
  protected:
   virtual ~StoragePartition() {}
 };
 
 }  // namespace content
 
 #endif  // CONTENT_PUBLIC_BROWSER_STORAGE_PARTITION_H_