path: root/src/network/socket/qabstractsocketengine_p.h
diff options
authorMartin Petersson <>2012-07-11 12:31:29 +0200
committerQt by Nokia <>2012-08-01 18:12:34 +0200
commitb8453b6fe3552cdfe32c726f87bb30d897c679b0 (patch)
tree544227e592bda31eaf8ba266f33f7cadb6336a45 /src/network/socket/qabstractsocketengine_p.h
parente178b49522465becf1b0c56bff1974e6037ba9ec (diff)
QtNetwork: Handle FD_CLOSE on Windows
We need to handle FD_CLOSE separately on Windows as this will be sent only once. When we get FD_CLOSE we need to check if there is more data available for reading. It there is this might indicate that there is another FD_READ that we need to handle after the FD_CLOSE. So in this case we will manually create another close event. Task-number: QTBUG-19409 Task-number: QTBUG-25386 Change-Id: Ie19906bc3f64fb6a85a508a5ab12caac5d70ccdb Reviewed-by: Shane Kearns <>
Diffstat (limited to 'src/network/socket/qabstractsocketengine_p.h')
1 files changed, 2 insertions, 0 deletions
diff --git a/src/network/socket/qabstractsocketengine_p.h b/src/network/socket/qabstractsocketengine_p.h
index 92d795408f..5264bc4479 100644
--- a/src/network/socket/qabstractsocketengine_p.h
+++ b/src/network/socket/qabstractsocketengine_p.h
@@ -71,6 +71,7 @@ public:
virtual ~QAbstractSocketEngineReceiver(){}
virtual void readNotification()= 0;
virtual void writeNotification()= 0;
+ virtual void closeNotification()= 0;
virtual void exceptionNotification()= 0;
virtual void connectionNotification()= 0;
@@ -173,6 +174,7 @@ public:
public Q_SLOTS:
void readNotification();
void writeNotification();
+ void closeNotification();
void exceptionNotification();
void connectionNotification();