Mojo Log service and a thread-safe client library.

mojo/services/log/interfaces/log.mojom

Index: mojo/services/log/interfaces/log.mojom
diff --git a/mojo/services/log/interfaces/log.mojom b/mojo/services/log/interfaces/log.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..d40fa1261d28ac6d8b55b852917a7b404ef71df5
--- /dev/null
+++ b/mojo/services/log/interfaces/log.mojom
@@ -0,0 +1,18 @@
+// 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.
+
+module mojo.log;
+
+import "log/interfaces/entry.mojom";
+
+// A log interface provides a way to do log source-code-level message entries. 
+// For example, this could be log messages generated from calling MOJO_LOG() in
+// C++.
+// TODO(vardhan):  How do we "globally silence" log entries issued by many
+// consumers of this interface?  Should |Log| provide controls for log levels?
+// or should clients register a "LogClientController" with this interface, and
+// |Log| will control their log levels?
+interface Log {
+  AddEntry(Entry entry);
+};