Pass through geofencing API calls to the content layer.

public/platform/WebGeofencingProvider.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 WebGeofencingProvider_h
+#define WebGeofencingProvider_h
+
+#include "public/platform/WebCallbacks.h"
+#include "public/platform/WebVector.h"
+
+namespace blink {
+
+struct WebGeofencingError;
+class WebGeofencingRegion;
+class WebString;
+
+typedef WebCallbacks<void, WebGeofencingError> WebGeofencingCallbacks;
+typedef WebCallbacks<WebVector<WebGeofencingRegion>, WebGeofencingError> WebGeofencingRegionsCallbacks;

[abarth-chromium, 2014/08/23 05:43:34]

Why callbacks and not a virtual interface?

[Marijn Kruisselbrink, 2014/08/25 22:25:25]

I'm not sure what kind of virtual interface you would expect, other than the
virtual interface with onSuccess() and onError(...) methods that WebCallbacks
is?
Also every other promise based API I've come across seems to use WebCallbacks
and CallbackPromiseAdapter to deal with resolving/rejecting the promise (the one
exception being the crypto API and its WebCryptoResult class, although I
wouldn't call that a virtual interface either).

+
+class WebGeofencingProvider {
+public:
+    virtual ~WebGeofencingProvider() { }
+
+    // Registers a region.
+    // Ownership of the WebGeofencingCallbacks is transferred to the client.
+    virtual void registerRegion(const WebGeofencingRegion&, WebGeofencingCallbacks*) = 0;
+
+    // Unregisters a region.
+    // Ownership of the WebGeofencingCallbacks is transferred to the client.
+    virtual void unregisterRegion(const WebString& regionId, WebGeofencingCallbacks*) = 0;
+
+    // Returns all the currently registered regions.
+    // Ownership of the WebGeofencingRegionsCallbacks is transferred to the client.
+    virtual void getRegisteredRegions(WebGeofencingRegionsCallbacks*) = 0;
+};
+
+} // namespace blink
+
+#endif // WebGeofencingProvider_h