debian-packages/eventcore
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Properly handle the case where a TCP connection gets immediately disconnected.

Browse source 
This can result in both, the write-ready and the disconnect events, to be triggered during the same event loop iteration.
This commit is contained in:
Sönke Ludwig 2017-01-30 22:52:13 +01:00
parent 773e09cd3d
commit 490dc15128
No known key found for this signature in database
GPG key ID: D95E8DB493EE314C
1 changed files with 2 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
source/eventcore/drivers/posix/sockets.d
View file

@ -108,9 +108,9 @@ final class PosixEventDriverSockets(Loop : PosixEventLoop) : EventDriverSockets
m_loop.setNotifyCallback!(EventType.write)(sock, null);
with (m_loop.m_fds[sock].streamSocket) {
state = ConnectionState.connected;
assert(connectCallback !is null);
connectCallback(cast(StreamSocketFD)sock, ConnectStatus.connected);
auto cb = connectCallback;
connectCallback = null;
if (cb) cb(cast(StreamSocketFD)sock, ConnectStatus.connected);
}
}
@ -253,13 +253,11 @@ final class PosixEventDriverSockets(Loop : PosixEventLoop) : EventDriverSockets
}
if (ret == 0 && buffer.length > 0) {
print("disconnect");
on_read_finish(socket, IOStatus.disconnected, 0);
return;
}
if (ret < 0 && mode == IOMode.immediate) {
print("wouldblock");
on_read_finish(socket, IOStatus.wouldBlock, 0);
return;
}