Add IPC stubs between browser and ServiceWorker's worker context in the child process

content/common/service_worker_interfaces.h

Index: content/common/service_worker_interfaces.h
diff --git a/content/common/service_worker_interfaces.h b/content/common/service_worker_interfaces.h
new file mode 100644
index 0000000000000000000000000000000000000000..d451af5654ff52099b1b9b3a54a8f9d314202a82
--- /dev/null
+++ b/content/common/service_worker_interfaces.h
@@ -0,0 +1,30 @@
+// Copyright 2013 The Chromium Authors. All rights reserved.

[alecflett, 2013/12/19 00:59:11]

Quite minor: the name of this file doesn't feel right to me. I wonder if this
could actually be service_worker.h or something? Maybe that's too general. Going
the other way, could this be service_worker_fetch.h ? maybe that's too specific.
I'm not sure.

[kinuko, 2013/12/20 08:01:09]

I was thinking about having 'common' types / definitions here that are to be
shared by browser and child process, though currently it only has FetchRequest. 
service_worker_types.h maybe?

+// 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_INTERFACES_H_
+#define CONTENT_COMMON_SERVICE_WORKER_INTERFACES_H_
+
+#include <map>
+#include <string>
+
+#include "base/basictypes.h"
+#include "content/common/content_export.h"
+#include "url/gurl.h"
+
+namespace content {
+
+struct CONTENT_EXPORT ServiceWorkerFetchRequest {
+  GURL url;
+  std::string method;
+  std::string referrer;

[alecflett, 2013/12/19 00:59:11]

What is referrer? Does it overlap with the "Referrer" header?
(I think that's ok, because I assume there are cases like https where there is
no actual referrer header but we still need it on onfetch? I did something very
similar in the prototype, as I was basically just following service_worker.ts)

We should just document that with a comment - explain if the 'referrer' header
is also present or not.

[kinuko, 2013/12/20 08:01:09]

Some of them are taken from old prototype code, but for now I removed most of
them other than 'url', 'method' and 'headers'.
(Again, this struct is basically for placeholder)

+  std::map<std::string, std::string> headers;
+  bool is_main_resource_load;
+
+  ServiceWorkerFetchRequest();

[alecflett, 2013/12/19 00:59:11]

If you're going to put constructors on this, is it worth putting a constructor
that just sets all the fields in one go?

[kinuko, 2013/12/20 08:01:09]

Yup. Will do when this struct/class's become more stable and it's actually used.

+  ~ServiceWorkerFetchRequest();
+};
+
+}  // namespace content
+
+#endif  // CONTENT_COMMON_SERVICE_WORKER_INTERFACES_H_