Add TCP socket mojo interfaces

mojo/services/public/interfaces/network/tcp_client_socket.mojom

Index: mojo/services/public/interfaces/network/tcp_client_socket.mojom
diff --git a/mojo/services/public/interfaces/network/tcp_client_socket.mojom b/mojo/services/public/interfaces/network/tcp_client_socket.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..2dd3544ac2a80f7f4ef5c302f967bc37811334a0
--- /dev/null
+++ b/mojo/services/public/interfaces/network/tcp_client_socket.mojom
@@ -0,0 +1,16 @@
+// Copyright 2014 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 {
+
+// Represents a TCP socket connected to a report system.

[wtc, 2014/10/03 22:37:43]

What is a "report system"? Did you mean a "remote system"?

+//
+// Reading and writing over the connection are done via the data pipe supplied
+// by the caller when creating the socket.

[willchan no longer on Chromium, 2014/10/06 21:52:39]

Should the mojo client have the ability to trigger a close() syscall on the
socket descriptor? Or does it need to close each datapipe individually (which
would trigger separate shutdown() syscall invocations for the read/write
directions)?

+interface TCPClientSocket {
+  // TODO(brettw) here we put options and whatnot for controlling the

[willchan no longer on Chromium, 2014/10/06 21:52:39]

Nit: s/whatnot/what not/

+  // connection.
+};
+
+}