AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove misleading documentation about QAbstractSocket::bytesWritten

Browse Source 
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>
This commit is contained in:
Thiago Macieira 2012-09-10 13:09:36 +02:00 committed by Qt by Nokia
parent 7fd0c52da7
commit 318b1a1d94
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/network/socket/qabstractsocket.cpp
View File

@ -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