Persist sessionStorage on disk.

content/public/browser/session_storage_namespace.h

Index: content/public/browser/session_storage_namespace.h
diff --git a/content/public/browser/session_storage_namespace.h b/content/public/browser/session_storage_namespace.h
index 5b17d0ceaebd56e8c45794931e5525c6d17d47f8..629ef84abcb5ed399adfcb00130d7e7f2f0ea4d4 100644
--- a/content/public/browser/session_storage_namespace.h
+++ b/content/public/browser/session_storage_namespace.h
@@ -16,6 +16,8 @@ namespace content {
 //       it keeps valgrind happy.
 class SessionStorageNamespace

[michaeln, 2012/05/30 01:29:19]

What if there were two different methods to manufacture an instance of this
class. One for use when creating completely new empty sessions and another for
use when re-animating a previously saved session given its persistent_id?

Would it make things more clear if this class had an id() and a persistent_id()
accessor?

[marja, 2012/05/31 14:41:34]

Done.

     : public base::RefCountedThreadSafe<SessionStorageNamespace> {
+ public:
+  virtual int64 id() const = 0;
  protected:
   friend class base::RefCountedThreadSafe<SessionStorageNamespace>;
   virtual ~SessionStorageNamespace() {}