Move push client to frame.

public/web/WebFrameClient.h

Index: public/web/WebFrameClient.h
diff --git a/public/web/WebFrameClient.h b/public/web/WebFrameClient.h
index c1198766c24db1cfabc587a0edc9a8cee143199b..bb33d26f2de258ac116badaff1d6f8ece88cee1d 100644
--- a/public/web/WebFrameClient.h
+++ b/public/web/WebFrameClient.h
@@ -79,6 +79,7 @@ class WebSocketHandle;
 class WebNode;
 class WebPlugin;
 class WebPluginPlaceholder;
+class WebPushClient;

[Peter Beverloo, 2014/11/11 18:23:28]

The PushClient currently has functionality for checking permission and
registering for push. Exactly which parts of this are going to be duplicated for
Frame vs. Workers?

[Michael van Ouwerkerk, 2014/11/12 12:05:25]

There will be no duplication. Requesting permission will hit this client, and
hop to the browser process to do that. Fetching the sender id from the manifest
will also hit this client, but will stay in the renderer to do that.

After that: register, unregister, getRegistration, and hasPermission will flow
through platform. The register call will use the sender id as input. It will be
rejected in the browser process if it turns out no permission was granted. This
way, all these calls can be run from both document and worker contexts.

 class WebRTCPeerConnectionHandler;
 class WebScreenOrientationClient;
 class WebSharedWorker;
@@ -589,6 +590,12 @@ public:
     // associated with the WebDataSource.
     virtual int64_t serviceWorkerID(WebDataSource&) { return -1; }
 
+
+    // Push API ------------------------------------------------------------

[Peter Beverloo, 2014/11/11 18:23:28]

You already have a Push API block around line 333.

[Michael van Ouwerkerk, 2014/11/12 12:05:25]

Done.

+
+    // Used to access the embedder for the Push API.
+    virtual WebPushClient* pushClient() { return 0; }
+
 protected:
     virtual ~WebFrameClient() { }
 };