Added TCPServerSocket.

net/socket/tcp_server_socket_libevent.h

+// Copyright (c) 2011 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.
+
+#ifndef NET_SOCKET_TCP_SERVER_SOCKET_LIBEVENT_H_
+#define NET_SOCKET_TCP_SERVER_SOCKET_LIBEVENT_H_
+
+#include "base/message_loop.h"
+#include "base/threading/non_thread_safe.h"
+#include "net/base/completion_callback.h"
+#include "net/socket/tcp_client_socket.h"
+
+namespace net {
+
+class IPEndPoint;
+
+class TCPServerSocketLibevent : public base::NonThreadSafe,
+                                public MessageLoopForIO::Watcher {
+ public:
+  TCPServerSocketLibevent(net::NetLog* net_log,
+                          const net::NetLog::Source& source);
+  ~TCPServerSocketLibevent();
+
+  // Bind the socket and start listening.

[willchan no longer on Chromium, 2011/04/13 16:08:51]

I guess it's implicit, but you might want to document that the way to stop
listening is to destroy the socket.

[Sergey Ulanov, 2011/04/13 21:20:19]

Done.

+  int Listen(const net::IPEndPoint& address, int backlog);
+
+  // Gets current address the socket is bound to.
+  int GetLocalAddress(IPEndPoint* address) const;
+
+  // Accept connection. Callback is called when new connection is
+  // accepted.
+  int Accept(TCPClientSocket** socket, IPEndPoint* address,

[willchan no longer on Chromium, 2011/04/13 16:08:51]

http://dev.chromium.org/developers/coding-style#Code_Formatting says:
For function declarations and definitions, put each argument on a separate line
unless everything fits on one line. You should only break this rule when the
arguments have some logical association like "int x, int y" or "char* str, int
str_len" where putting a few arguments together makes semantic sense.  Do NOT
collapse function arguments together just because you have "too many":

What do you think about using a scoped_ptr<TCPClientSocket>* instead to indicate
ownership of the result? And is this |address| parameter necessary? Can't we get
this by ClientSocket::GetPeerAddress()? Or do you think it'll be used often?

[Sergey Ulanov, 2011/04/13 21:20:19]

Done.
Done
In most cases caller would need the address, but I don't see the reason why
GetPeerAddress() cannot be used. I was initially thinking that having it here
would save us one syscall, but it's not the case because GetPeerAddress()
doesn't make any syscalls.

+             CompletionCallback* callback);
+
+  // MessageLoopForIO::Watcher implementation.
+  virtual void OnFileCanReadWithoutBlocking(int fd);
+  virtual void OnFileCanWriteWithoutBlocking(int fd);
+
+ private:
+  int AcceptInternal(TCPClientSocket** socket, net::IPEndPoint* address);
+  void Close();
+
+  int socket_;
+
+  MessageLoopForIO::FileDescriptorWatcher accept_socket_watcher_;
+
+  TCPClientSocket** accept_socket_;
+  IPEndPoint* accept_address_;
+  CompletionCallback* accept_callback_;
+
+  net::NetLog* net_log_;
+  net::NetLog::Source net_log_source_;
+};
+
+}  // namespace net
+
+#endif  // NET_SOCKET_TCP_SERVER_SOCKET_LIBEVENT_H_