Define push_messaging module with PushManager skeleton.

Source/modules/push_messaging/NavigatorPushManager.h

+// Copyright 2014 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef NavigatorPushManager_h
+#define NavigatorPushManager_h
+
+#include "platform/Supplementable.h"
+
+namespace WebCore {
+
+class Navigator;
+class PushManager;
+
+class NavigatorPushManager FINAL : public Supplement<Navigator> {

[Peter Beverloo, 2014/03/26 21:35:35]

WillBeHeapSupplement? Then include the WILL_BE_USING_GARBAGE_COLLECTED_MIXIN
define, use RefPtrWillBeMember<> instead of RefPtr<>, and so on. I don't think
there's a very strong reason not to do this yet, and there are plenty of
examples in other modules around.

[Michael van Ouwerkerk, 2014/03/27 19:15:24]

Done.

+public:
+    virtual ~NavigatorPushManager();
+    static NavigatorPushManager& from(Navigator&);
+
+    static PushManager* push(Navigator&);
+    PushManager* pushManager() const;
+
+private:
+    NavigatorPushManager();
+    static const char* supplementName();
+
+    mutable RefPtr<PushManager> m_pushManager;

[Peter Beverloo, 2014/03/26 21:35:35]

While there is some precedence, not declaring pushManager() as const is cleaner,
since it's not. That'd allow you to get rid of the mutable here.

[Michael van Ouwerkerk, 2014/03/27 19:15:24]

Done.

+};
+
+} // namespace WebCore
+
+#endif // NavigatorPushManager_h