Mojoify FetchEvent of Service Worker.

content/common/service_worker/fetch_event_dispatcher.mojom

Index: content/common/service_worker/fetch_event_dispatcher.mojom
diff --git a/content/common/service_worker/fetch_event_dispatcher.mojom b/content/common/service_worker/fetch_event_dispatcher.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..59d0ed1891797d4f49fd904dca578bb1c8fc5c07
--- /dev/null
+++ b/content/common/service_worker/fetch_event_dispatcher.mojom
@@ -0,0 +1,17 @@
+// Copyright 2016 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.
+
+module content.mojom;
+
+import "mojo/common/common_custom_types.mojom";
+import "third_party/WebKit/public/platform/modules/serviceworker/service_worker_event_status.mojom";
+
+[Native]
+struct ServiceWorkerFetchRequest;
+
+interface FetchEventDispatcher {

[dcheng, 2016/09/30 08:54:43]

Is there an overall design doc of how SW will work in Mojo? This seems like a
very small interface, and I'm wondering if it would make more sense as part of a
larger SW interface?

[horo, 2016/10/03 02:30:57]

shimazu@ is working on the Mojofication of SW.
BUG: https://crbug.com/629701
design doc:
https://docs.google.com/document/d/1DwPpvZG1gTCk5JAULmjPf0eCOHt01Pk59YdwRrbQW...

We don't think we can mojofy all SW events so quickly.
But the priority of "navigation preload" which needs Mojo is high.
(We will use Mojo's datapipe to pass the preloaded response to the SW.)

So we want to mojofy FetchEvent before mojofying all SW events.

SyncEvent has been already mojofied (crbug.com/479251)
So this CL is using the similar approach.

+  DispatchFetchEvent(int32 response_id, ServiceWorkerFetchRequest request)
+      => (blink.mojom.ServiceWorkerEventStatus status,
+          mojo.common.mojom.Time dispatch_event_time);
+};