Expose distiller functions to JavaScript

components/dom_distiller/content/common/distiller_javascript_service.mojom

Index: components/dom_distiller/content/common/distiller_javascript_service.mojom
diff --git a/content/public/common/service_worker_event_status.mojom b/components/dom_distiller/content/common/distiller_javascript_service.mojom
similarity index 62%
copy from content/public/common/service_worker_event_status.mojom
copy to components/dom_distiller/content/common/distiller_javascript_service.mojom
index 020d0e82e88cbb9dd52b2cf53651b629136a8910..a32551b9829dcc1a85ec32eb8510432d0c935bb5 100644
--- a/content/public/common/service_worker_event_status.mojom
+++ b/components/dom_distiller/content/common/distiller_javascript_service.mojom
@@ -2,11 +2,8 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-module content;
+module dom_distiller;
 
-enum ServiceWorkerEventStatus {
-  COMPLETED,
-  REJECTED,
-  ABORTED,
-  MAX=ABORTED
+interface DistillerJavaScriptService {

[nyquist, 2015/08/19 10:59:54]

It would be helpful with a short description saying which end of the service
this is in. Is this running in the context of the renderer? Or in the browser
process?

The direction of these mojo-service seems to confuse me every time I look at
these services, and I guess a quick comment here would help me get my bearings
right (same for the other .mojom file).

[mdjones, 2015/08/19 20:25:19]

Done.

+  HandleDistillerEchoCall(string message);
 };