Alex Trotsenko bec47545dc QAbstractSocket: do not fail writing on read buffer overflow ... canReadNotification() could return 'false' if either the socket has been closed, or the read buffer has reached the maximum size. Because of this duality, waitForBytesWritten() should not fail as a result of a canReadNotification() call. Change-Id: I9a15fa174a3b982a7ce404913caa38fc19f64622 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com> Reviewed-by: Markus Goetz (Woboq GmbH) <markus@woboq.com>		2016-03-18 13:05:42 +00:00
..
platformsocketengine	Add Intel copyright to files that Intel has had non-trivial contribution	2016-01-21 22:44:21 +00:00
qabstractsocket	Updated license headers	2016-01-21 18:55:18 +00:00
qhttpsocketengine	Merge "Merge remote-tracking branch 'origin/5.6' into dev" into refs/staging/dev	2016-01-26 11:27:37 +00:00
qlocalsocket	Merge remote-tracking branch 'origin/5.6' into 5.7	2016-03-11 20:08:50 +01:00
qsocks5socketengine	Updated license headers	2016-01-21 18:55:18 +00:00
qtcpserver	Updated license headers	2016-01-21 18:55:18 +00:00
qtcpsocket	QAbstractSocket: do not fail writing on read buffer overflow	2016-03-18 13:05:42 +00:00
qudpsocket	Updated license headers	2016-01-21 18:55:18 +00:00
socket.pro	WinRT: Fixed compilation of network autotests and benchmarks	2013-12-06 15:06:47 +01:00