Details
-
Bug
-
Resolution: Cannot Reproduce
-
P3: Somewhat important
-
None
-
5.13.2
-
None
Description
When we connect two QTcpSockets lest name it sock1 and sock2 and then for sock1 we call consequently:
sock1->write(...);
sock1->flush();
sock1->close();
The sock2 receive signals in the following sequence:
- QAbstractSocket::error(RemoteHostClosedError)
- QAbstractSocket::disconnected
- QAbstractSocket::readyRead
This order is confusing because after socket error hard to expect new data arriving and socket usually is closed. So the application with sock2 will not receive the message.