Add TCP socket mojo interfaces

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

+// 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.
+
+import "mojo/services/public/interfaces/network/net_address.mojom"
+import "mojo/services/public/interfaces/network/network_error.mojom"
+import "mojo/services/public/interfaces/network/tcp_client_socket.mojom"
+
+module mojo {
+
+// Represents a TCP server socket listening for incoming requests.
+[Client=TCPServerSocketClient]
+interface TCPServerSocket {
+  // Accepts an incoming connection request and hooks up a TCPClientSocket for
+  // connecting with the remote host. This function is called in reponse to
+  // OnConnectionAvailable().
+  //
+  // On success, the address of the remote host will be provided.
+  AcceptConnection(handle<data_pipe_consumer> send_stream,
+                   handle<data_pipe_producer> receive_stream,
+                   TCPClientSocket& client_socket)

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

Nit: it is confusing that TCPServerSocket::AcceptConnection operates on a
TCPClientSocket. This is a naming issue. I hope we can come up with a better
name for a socket (either client or server side) that has been connected to the
peer.

One idea is TCPConnectedSocket. This name has one issue -- if the class has an
IsConnected() method, that can also be confusing. But it seems less confusing
than using a TCPClientSocket on the server side.

+      => (NetworkError result, NetAddress? remote_address);
+};
+
+interface TCPServerSocketClient {
+  // Notifies the client that an incoming connection is available.
+  //
+  // The client should call AcceptConnection() to accept the request.
+  OnConnectionAvailable();
+
+  // TODO(brettw) probably need some error reporting function here.
+};
+
+}