Rename WebServiceWorkerRegistry to WebServiceWorkerProvider

public/platform/WebServiceWorkerProvider.h

Index: public/platform/WebServiceWorkerProvider.h
diff --git a/public/platform/WebServiceWorkerRegistry.h b/public/platform/WebServiceWorkerProvider.h
similarity index 83%
copy from public/platform/WebServiceWorkerRegistry.h
copy to public/platform/WebServiceWorkerProvider.h
index 3ac2dad5858336c36a33c743e6e29864f8aeea49..c7f0dc06fa7d05b8a6a356290cdc677a75f6bb78 100644
--- a/public/platform/WebServiceWorkerRegistry.h
+++ b/public/platform/WebServiceWorkerProvider.h
@@ -28,8 +28,8 @@
  * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  */
 
-#ifndef WebServiceWorkerRegistry_h
-#define WebServiceWorkerRegistry_h
+#ifndef WebServiceWorkerProvider_h
+#define WebServiceWorkerProvider_h
 
 #include "public/platform/WebCallbacks.h"
 
@@ -39,12 +39,13 @@ class WebString;
 class WebURL;
 class WebServiceWorker;
 
-class WebServiceWorkerRegistry {
+class WebServiceWorkerProvider {
 public:
     typedef WebCallbacks<WebServiceWorker, WebServiceWorker> WebServiceWorkerCallbacks;
-    virtual void registerServiceWorker(const WebString& pattern, const WebURL& scriptUrl, WebServiceWorkerCallbacks*) { }
+    virtual void registerServiceWorker(const WebURL& pattern, const WebURL& scriptUrl, WebServiceWorkerCallbacks*) { }

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

I don't understand.  A pattern is something different from a URL.  A pattern
stands for a set of URLs, not a single URL.

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

Well for now WebURL is about the closest container we have, and we don't expect
to change it until we get some developer feedback. 

I could switch back to strings, but I feel like that drops even more semantics
than WebURL, and would just be sending a url string that would be
reconsistituted into a URL on the other side again:
https://github.com/slightlyoff/ServiceWorker/blob/master/explainer.md#urls-do...

We may possibly think about something like this:
http://developer.chrome.com/extensions/match_patterns.html but we don't really
know right now. Also, we know we're going to have to evaluate the pattern
browser-side, but we don't' know if we'll also want to evaluate it blink-side,
for instance if we need to synchronously decide if a pattern is valid or not.

Would it be alright if I use WebURL for now and change later once we know more?

 
-    virtual void unregisterServiceWorker(const WebString& pattern, WebServiceWorkerCallbacks*) { }
+    virtual void unregisterServiceWorker(const WebURL& pattern, WebServiceWorkerCallbacks*) { }
+    virtual ~WebServiceWorkerProvider() { }
 };
 
 } // namespace WebKit