Persist sessionStorage on disk.

content/browser/browser_context.cc

Index: content/browser/browser_context.cc
diff --git a/content/browser/browser_context.cc b/content/browser/browser_context.cc
index 19dcf236104ed73e3bd5601d79d6cd48cc8a113c..743286d097b285041da2b549708d56826e577f7d 100644
--- a/content/browser/browser_context.cc
+++ b/content/browser/browser_context.cc
@@ -86,7 +86,8 @@ void CreateQuotaManagerAndClients(BrowserContext* context) {
 
   FilePath path = context->IsOffTheRecord() ? FilePath() : context->GetPath();
   scoped_refptr<DOMStorageContextImpl> dom_storage_context =
-      new DOMStorageContextImpl(path, context->GetSpecialStoragePolicy());
+      new DOMStorageContextImpl(path, context->GetSpecialStoragePolicy(),
+                                context->ShouldSaveSessionStorageOnDisk());

[jam, 2012/07/11 15:51:35]

how about instead of adding a method to the BrowserContext API (which I've tried
to keep minimal), you add a setter for this on content::DOMStorageContext? that
interface already has a method related to session restore.

so kind of like how it's done for cookies: 
http://code.google.com/searchframe#OAMlx_jo-ck/src/chrome/browser/profiles/pr...

[jochen (gone - plz use gerrit), 2012/07/11 17:52:16]

Cookies are a bad role model here: in contrast to all other storage APIs, the
embedder has to provide a persistent store for cookies.

Everything else persists stuff to disk iff the browser context has a path
defined.

The situation here is that an embedder might want to provide a path to have
regular data stored on disk, but would prefer not to persist sessionStorage.
This is different from the flag that is passed to the cookie monster (or the
other storage systems) that just controls how shutdown/startup is handled, but
doesn't change whether a file backend is created or not.

The problem with setting this flag on the DOM storage context directly is that
it needs to be passed to the constructor. The DOM storage context, however, is
created lazily. The embedder would need to invoke this method early enough,
requiring detailed information on how the browser context is implemented.

[jam, 2012/07/11 21:40:28]

I see. It seems that this can be changed so that it's not required at
construction, but just has to be set before it's used? i.e. it's the embedder
who creates a BrowserContext, so if they want to set this, they can do so soon
after before they use it.

[marja, 2012/07/12 09:22:03]

Done.

   context->SetUserData(
       kDOMStorageContextKeyName,
       new UserDataAdapter<DOMStorageContextImpl>(dom_storage_context));
@@ -268,4 +269,8 @@ BrowserContext::~BrowserContext() {
     GetDownloadManager(this)->Shutdown();
 }
 
+bool BrowserContext::ShouldSaveSessionStorageOnDisk() const {
+  return false;
+}
+
 }  // namespace content