QTcpSocket: confusing signals sequence

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:

1. QAbstractSocket::error(RemoteHostClosedError)
2. QAbstractSocket::disconnected
3. 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.