gpt4 book ai didi

c - 非阻塞Socket连接总是成功?

转载 作者:行者123 更新时间:2023-11-30 17:03:10 33 4
gpt4 key购买 nike

如果之前有人问过这个问题,我深表歉意。我正在使用选择多路复用编写一个非阻塞套接字客户端。让我困惑的一件事是,无论服务器在线还是离线,非阻塞连接总是成功。我搜索了很多帖子并遵循了他们的解决方案,但没有一个在我的 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

}

每次选择返回并调用此回调时,该回调总是成功,即进入“准备写/读” block ,而不是失败。为什么会发生这种情况?如何设计一个可移植的机制来检测连接是否真的成功?下面是我创建连接器的方法。

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;
}

最佳答案

Everytime the select returns and invokes this callback which always succeeds, i.e., going to the "Ready to write/read" block, instead of cerring failure. Why can this happen?

当异步 TCP 连接正在进行时(如 connect() 调用中的 -1/EINPROGRESS 所示),您应该将套接字传递给 select() 作为其准备写入套接字集的一部分,以便当套接字指示它已准备好写入时,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() 如上所述,但如果您想收到有关在 Windows 下失败的异步 connect() 尝试,您还需要在“异常(exception)”fd_set 下注册套接字,因为 Windows 将使用“异常(exception)”fd_set 来传达失败的异步 connect()。

关于c - 非阻塞Socket连接总是成功?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/36253705/

33 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com