diff options
author | Thiago Macieira <thiago.macieira@intel.com> | 2012-09-10 13:09:36 +0200 |
---|---|---|
committer | Qt by Nokia <qt-info@nokia.com> | 2012-09-10 14:09:45 +0200 |
commit | 318b1a1d94dd9293f1e9345e34b5d9b6c47ec581 (patch) | |
tree | 346c8cd42b39d17e4f5c3a21dbbc7bbe3e7c2340 | |
parent | 7fd0c52da7acd9a945bf0cc5fbadabfd0d4fafa4 (diff) |
Remove misleading documentation about QAbstractSocket::bytesWritten
The signal has nothing to do with any action on the remote side. It is
emitted when the class has written the bytes to the operating system.
More likely than not, the bytes have not been even sent yet, much less
read by the other side.
Change-Id: Ia04d37ffc8c0788173d3d29f49c5759bcdef6afa
Reviewed-by: Qt Doc Bot <qt_docbot@qt-project.org>
Reviewed-by: Shane Kearns <shane.kearns@accenture.com>
-rw-r--r-- | src/network/socket/qabstractsocket.cpp | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/src/network/socket/qabstractsocket.cpp b/src/network/socket/qabstractsocket.cpp index a7f9ceb3c4..c06ce9cddd 100644 --- a/src/network/socket/qabstractsocket.cpp +++ b/src/network/socket/qabstractsocket.cpp @@ -95,10 +95,9 @@ convenience functions readLine() and readAll(). QAbstractSocket also inherits getChar(), putChar(), and ungetChar() from QIODevice, which work on single bytes. The bytesWritten() signal - is emitted when data has been written to the socket (i.e., when - the client has read the data). Note that Qt does not limit the - write buffer size. You can monitor its size by listening to this - signal. + is emitted when data has been written to the socket. Note that Qt does + not limit the write buffer size. You can monitor its size by listening + to this signal. The readyRead() signal is emitted every time a new chunk of data has arrived. bytesAvailable() then returns the number of bytes |