Gather the ServiceWorker client information in the browser process.

content/common/service_worker/service_worker_traits.h

Index: content/common/service_worker/service_worker_traits.h
diff --git a/content/common/service_worker/service_worker_traits.h b/content/common/service_worker/service_worker_traits.h
new file mode 100644
index 0000000000000000000000000000000000000000..4326c2005f9560871aa35355d5e440ca55a4d27b
--- /dev/null
+++ b/content/common/service_worker/service_worker_traits.h
@@ -0,0 +1,27 @@
+// Copyright 2015 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 CONTENT_COMMON_SERVICE_WORKER_SERVICE_WORKER_TRAITS_H_
+#define CONTENT_COMMON_SERVICE_WORKER_SERVICE_WORKER_TRAITS_H_
+
+#include "ipc/ipc_message.h"
+#include "ipc/ipc_param_traits.h"
+
+namespace content {
+class ServiceWorkerClientInfo;
+}
+
+namespace IPC {
+
+template <>

[Tom Sepez, 2015/01/23 17:51:43]

This is a step in the wrong direction, as we want to eliminate hand-written
traits and the possibility for errors that the introduce. This brings us
directly into conflict between making IPC easy and doing the information hiding
that C++ folks like.  Do you absolutely need info hiding here?  Otherwise making
them public and continuing to use macros avoids IPC issues.

[mlamouri (slow - plz ping), 2015/01/23 18:41:07]

I guess I could have all the properties public for the sake of IPC but still
recommend to not use them directly.

michaeln@, WDYT?

+struct ParamTraits<content::ServiceWorkerClientInfo> {
+  typedef content::ServiceWorkerClientInfo param_type;
+  static void Write(Message* m, const param_type& p);
+  static bool Read(const Message* m, PickleIterator* iter, param_type* r);
+  static void Log(const param_type& p, std::string* l);
+};
+
+} // namespace IPC
+
+#endif  // CONTENT_COMMON_SERVICE_WORKER_SERVICE_WORKER_TRAITS_H_