Add TCP socket mojo interfaces

mojo/services/public/interfaces/network/tcp_bound_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"
+import "mojo/services/public/interfaces/network/tcp_server_socket.mojom"
+
+module mojo {
+
+// Represents a TCP socket that is bound to a local address and port, but
+// is not yet in a listening or connected state.
+//
+// A bound socket can be used to create a server socket listening on the
+// local address, or it can be used to create a client socket by connecting to
+// a remote host.
+interface TCPBoundSocket {
+  // Puts the socket into server mode, awaiting incoming connections.
+  //
+  // Once this function is called, neither StartListening nor Connect can be
+  // used on this socket again.
+  StartListening(TCPServerSocket& server);

[yzshen1, 2014/10/02 00:21:46]

Does it need a callback reporting NetworkError?

[brettw, 2014/10/02 04:09:30]

I'm going to do the implementation and see what we need here. I'm guessing an
error callback on the ServerSocketClient can handle this case, since I think we
will need to be able to handle the case where an error happens while we're
listening. But if that can't happen and StartListening can fail, I'll add the
error to a callback here instead. 

+
+  // Puts this socket into client mode by connecting to a remote host. If you
+  // do not care about the local address or port, you can call
+  // NetworkService.CreateTCPClientSocket to connect directly and skip the
+  // "bound" state.
+  //
+  // Once this function is called, neither StartListening nor Connect can be
+  // used on this socket again.
+  Connect(NetAddress remote_address,
+          handle<data_pipe_consumer> send_stream,
+          handle<data_pipe_producer> receive_stream,
+          TCPClientSocket& client_socket)
+      => (NetworkError result);
+};
+
+}