无阻塞套接字连接总是成功吗?

时间:2016-03-27 23:01:32

标签: c sockets network-programming nonblocking

如果以前曾问过这个问题,我会道歉。我正在使用select multiplexing编写一个非阻塞套接字客户端。令我困惑的一件事是,无论服务器在线还是离线,非阻塞连接总是成功的。我搜索了许多帖子,并按照他们的解决方案,但没有一个在我的linux ubuntu机器上工作。

static void callback_on_select_write(int connect_fd) {

  // Client write event arrived;

  int error = -1;
  socklen_t len = sizeof(error);

  if(getsockopt(connect_fd, SOL_SOCKET, SO_ERROR, &error, &len) == -1) {
    return;
  }

  // getsockopt puts the errno value for connect into erro so 0 means no-error. 
  if(error == 0) {
      // Connection ok.
  }
  else {
    cerr << "Failed to connect\n";
    return;
  }

  // Ready to write/read

}

每次select返回并调用总是成功的回调,即进入&#34;准备写/读&#34;阻止,而不是cerring失败。为什么会这样?如何设计便携式机制来检测连接是否真的成功?以下是我创建连接器的方式。

int make_socket_client(const ::std::string& hostname, const ::std::string& port) {

  struct addrinfo hints;
  struct addrinfo* res {nullptr};
  struct addrinfo* ptr {nullptr};

  memset(&hints, 0, sizeof(struct addrinfo));
  hints.ai_family = AF_UNSPEC;
  hints.ai_socktype = SOCK_STREAM;
  hints.ai_protocol = IPPROTO_TCP;

  int rv;
  int connector;

  if((rv = getaddrinfo(hostname.c_str(), port.c_str(), &hints, &res)) != 0) {
    return -1;
  }

  // Try to get the first available client connection.
  for(ptr = res; ptr != nullptr; ptr = ptr->ai_next) {

    // Ignore undefined ip type.
    if(ptr->ai_family != AF_INET && ptr->ai_family != AF_INET6) {
      continue;
    }

    // Create a listener socket and bind it to the localhost as the server.
    if((connector = socket(ptr->ai_family, ptr->ai_socktype, ptr->ai_protocol)) == -1){
      continue;
    }

    make_fd_nonblocking(connector);

    if(connect(connector, (struct sockaddr*)ptr->ai_addr, ptr->ai_addrlen) < 0) {
      // This is what we expect.
      if(errno == EINPROGRESS) {
        break;
      }
      else {
        close(connector);
        continue;
      }
    }
    else {
      break;
    }
  }

  freeaddrinfo(res);

  if(ptr == nullptr) {
    return -1;
  }

  return connector;  
}

1 个答案:

答案 0 :(得分:0)

  

每次select返回并始终调用此回调   成功,即进入&#34;准备写/读&#34;阻止,而不是   切断失败。为什么会发生这种情况?

当异步TCP连接正在进行时(由connect()调用中的-1 / EINPROGRESS指示),您应该将套接字传递给select()作为其ready-for-write套接字集的一部分,以便当套接字指示它已准备好写入时,select()将返回。

当TCP连接成功或失败时,select()将返回套接字已准备好写入(*)。当发生这种情况时,您需要弄清楚发生了两种可能的结果(成功或失败)中的哪一种。

下面是我将异步连接的套接字select()作为准备写入时调用的函数。

// call this select() has indicated that (fd) is ready-for-write because
// (fd)'s asynchronous-TCP connection has either succeeded or failed.
// Returns true if the connection succeeded, false if the connection failed.
// If this returns true, you can then continue using (fd) as a normal
// connected/non-blocking TCP socket.  If this returns false, you should
// close(fd) because the connection failed.
bool FinalizeAsyncConnect(int fd)
{
#if defined(__FreeBSD__) || defined(BSD)
   // Special case for FreeBSD7, for which send() doesn't do the trick
   struct sockaddr_in junk;
   socklen_t length = sizeof(junk);
   memset(&junk, 0, sizeof(junk));
   return (getpeername(fd, (struct sockaddr *)&junk, &length) == 0);
#else
   // For most platforms, the code below is all we need
   char junk;
   return (send(fd, &junk, 0, 0L) == 0);
#endif
}

(*)附注:Windows下的情况略有不同,因为Windows喜欢以自己的方式做事:在Windows下,如上所述指示成功的异步connect(),但是如果您想要收到有关a的通知在Windows下失败的异步connect()尝试,你需要在&#34;下注册你的套接字,除了&#34; fd_set也是,因为它是&#34;除了&#34; Windows将用于传递失败的异步连接()的fd_set。