Another stab at the Chromium side of storage events. The WebKit side can be ...

chrome/browser/in_process_webkit/webkit_context.h

Index: chrome/browser/in_process_webkit/webkit_context.h
===================================================================
--- chrome/browser/in_process_webkit/webkit_context.h	(revision 27652)
+++ chrome/browser/in_process_webkit/webkit_context.h	(working copy)
@@ -10,6 +10,7 @@
 #include "base/scoped_ptr.h"
 
 class DOMStorageContext;
+class WebKitThread;
 
 // There's one WebKitContext per profile.  Various DispatcherHost classes
 // have a pointer to the Context to store shared state.
@@ -19,10 +20,10 @@
 
   const FilePath& data_path() const { return data_path_; }
   bool is_incognito() const { return is_incognito_; }
+  DOMStorageContext* dom_storage_context() {
+    return dom_storage_context_.get();
+  }
 
-  // Initialized lazily.  Pointer is valid for the lifetime of this instance.
-  DOMStorageContext* GetDOMStorageContext();
-
  private:
   friend class base::RefCountedThreadSafe<WebKitContext>;
   ~WebKitContext();
@@ -31,7 +32,6 @@
   const FilePath data_path_;
   const bool is_incognito_;
 
-  // The state for DOM Storage.
   scoped_ptr<DOMStorageContext> dom_storage_context_;
 
   DISALLOW_IMPLICIT_CONSTRUCTORS(WebKitContext);