Rename WebServiceWorkerRegistry to WebServiceWorkerProvider

Source/modules/serviceworkers/NavigatorServiceWorker.h

Index: Source/modules/serviceworkers/NavigatorServiceWorker.h
diff --git a/Source/modules/serviceworkers/NavigatorServiceWorker.h b/Source/modules/serviceworkers/NavigatorServiceWorker.h
index ef60deecfaa2d63c1ce199f79b796da13aec2fb6..22b3c851164f114392c2b11e91894502f8690c3e 100644
--- a/Source/modules/serviceworkers/NavigatorServiceWorker.h
+++ b/Source/modules/serviceworkers/NavigatorServiceWorker.h
@@ -35,6 +35,11 @@
 #include "core/page/Navigator.h"
 #include "platform/Supplementable.h"
 
+namespace WebKit {
+class WebServiceWorkerProvider;
+class WebServiceWorkerProviderClient;
+}
+
 namespace WebCore {
 
 class ExceptionState;
@@ -55,9 +60,12 @@ private:
 
     explicit NavigatorServiceWorker(Navigator*);
 
+    WebKit::WebServiceWorkerProvider* serviceWorkerProvider();

[abarth-chromium, 2013/10/11 18:08:14]

Sometimes we call functions like this ensureProvider() to indicate that it will
create m_provider if it's not there already.

[alecflett, 2013/10/11 18:52:23]

Done.

+
     static const char* supplementName();
 
     Navigator* m_navigator;
+    OwnPtr<WebKit::WebServiceWorkerProvider> m_provider;

[abarth-chromium, 2013/10/11 18:08:14]

I don't understand how m_provider is cleaned up.  Don't we need to drop
m_provider when we get detached from the frame?  Otherwise we'll try to talk to
the m_provide after the WebFrame has been torn down.  Presumably you need to
subclass DOMWindowProperty and watch for willDetachGlobalObjectFromFrame and
willDestroyGlobalObjectInFrame like DOMWindowIndexedDatabase does:

void DOMWindowIndexedDatabase::willDetachGlobalObjectFromFrame()
{
    m_idbFactory = nullptr;
    DOMWindowProperty::willDetachGlobalObjectFromFrame();
}

[alecflett, 2013/10/11 18:52:23]

Done. This hangs off navigator, but I assume it's ok to use navigator->frame()
in the constructor here.

 };
 
 } // namespace WebCore