Pass through geofencing API calls to the browser process.

content/common/geofencing_messages.h

Index: content/common/geofencing_messages.h
diff --git a/content/common/geofencing_messages.h b/content/common/geofencing_messages.h
new file mode 100644
index 0000000000000000000000000000000000000000..a88ecaae4c3b12a574672ba5516d3301a74cfa92
--- /dev/null
+++ b/content/common/geofencing_messages.h
@@ -0,0 +1,61 @@
+// 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.
+
+// IPC message for geofencing
+// Multiply-included message file, hence no include guard.
+
+#include "content/common/geofencing_status.h"
+#include "ipc/ipc_message_macros.h"
+#include "third_party/WebKit/public/platform/WebCircularGeofencingRegion.h"
+
+#define IPC_MESSAGE_START GeofencingMsgStart
+
+IPC_ENUM_TRAITS_MAX_VALUE(content::GeofencingStatus,
+                          content::GEOFENCING_STATUS_LAST)
+
+IPC_STRUCT_TRAITS_BEGIN(blink::WebCircularGeofencingRegion)
+  IPC_STRUCT_TRAITS_MEMBER(latitude)
+  IPC_STRUCT_TRAITS_MEMBER(longitude)
+  IPC_STRUCT_TRAITS_MEMBER(radius)
+IPC_STRUCT_TRAITS_END()
+
+typedef std::map<std::string, blink::WebCircularGeofencingRegion>
+    GeofencingRegistrations;
+
+// Messages sent from the child process to the browser.
+IPC_MESSAGE_CONTROL4(GeofencingHostMsg_RegisterRegion,
+                     int /* thread_id */,
+                     int /* request_id */,
+                     std::string /* region_id */,

[palmer, 2014/09/25 19:44:12]

What is the lexical/syntactic structure of these strings?

(Where possible, I always seek to use some more constrained type.)

[Marijn Kruisselbrink, 2014/09/25 19:55:23]

Currently these strings are completely unrestricted. It's up to websites to
attach meaning/structure to their region ids. Although we'll probably need to
add some restrictions on what websites can do with this field; having
multi-megabyte IDs certainly would be problematic; this isn't a part that is
very well specced out yet, so any suggestions are welcome.

+                     blink::WebCircularGeofencingRegion /* region */)
+
+IPC_MESSAGE_CONTROL3(GeofencingHostMsg_UnregisterRegion,
+                     int /* thread_id */,
+                     int /* request_id */,
+                     std::string /* regionId */)

[palmer, 2014/09/25 19:44:12]

Nit: "region_id"

[Marijn Kruisselbrink, 2014/09/25 19:55:23]

Done.

+
+IPC_MESSAGE_CONTROL2(GeofencingHostMsg_GetRegisteredRegions,
+                     int /* thread_id */,
+                     int /* request_id */)
+
+// Messages sent from the browser to the child process.
+
+// Reply in response to GeofencingHostMsg_RegisterRegion
+IPC_MESSAGE_CONTROL3(GeofencingMsg_RegisterRegionComplete,
+                     int /* thread_id */,
+                     int /* request_id */,
+                     content::GeofencingStatus /* status */)
+
+// Reply in response to GeofencingHostMsg_UnregisterRegion
+IPC_MESSAGE_CONTROL3(GeofencingMsg_UnregisterRegionComplete,
+                     int /* thread_id */,
+                     int /* request_id */,
+                     content::GeofencingStatus /* status */)
+
+// Reply in response to GeofencingHostMsg_GetRegisteredRegions
+IPC_MESSAGE_CONTROL4(GeofencingMsg_GetRegisteredRegionsComplete,
+                     int /* thread_id */,
+                     int /* request_id */,
+                     content::GeofencingStatus /* status */,
+                     GeofencingRegistrations /* regions */)