The QSocketNotifier class provides support for monitoring activity on a file descriptor. This class makes it possible to integrate the event loop with other event loops based on file descriptors. File descriptor action is detected in the CopperSpice main event loop from QCoreApplication::exec().

Once you have opened a device using a low-level (usually platform-specific) API, you can create a socket notifier to monitor the file descriptor. The socket notifier is enabled by default, i.e. it emits the activated() signal whenever a socket event corresponding to its type occurs. Connect the activated() signal to the slot you want to be called when an event corresponding to your socket notifier's type occurs.

There are three types of socket notifiers: read, write, and exception. The type is described by the Type enum, and must be specified when constructing the socket notifier. After construction it can be determined using the type() method. If you need to monitor both reads and writes for the same file descriptor, you must create two socket notifiers. It is not possible to install two socket notifiers of the same type (Read, Write, Exception) on the same socket.

The setEnabled() method allows you to disable as well as enable the socket notifier. It is generally advisable to explicitly enable or disable the socket notifier, especially for write notifiers. A disabled notifier ignores socket events (the same effect as not creating the socket notifier). Use the isEnabled() function to determine the notifier's current status.

Finally, you can use the socket() function to retrieve the socket identifier. Although the class is called QSocketNotifier, it is normally used for other types of devices than sockets. QTcpSocket and QUdpSocket provide notification through signals, so there is normally no need to use a QSocketNotifier on them.

Windows OS

The socket passed to QSocketNotifier will become non-blocking, even if it was created as a blocking socket. The activated() signal is sometimes triggered by high general activity on the host, even if there is nothing to read. A subsequent read from the socket can then fail, the error indicating that there is no data available (e.g., WSAEWOULDBLOCK). This is an operating system limitation and not a bug in QSocketNotifier.

To ensure the socket notifier handles read notifications correctly, follow these steps when you receive a notification.

1. Disable the notifier.
2. Read data from the socket.
3. Re-enable the notifier if you are interested in more data (such as after having written a new command to a remote server).

To ensure the socket notifier handles write notifications correctly, follow these steps when you receive a notification.

1. Disable the notifier.
2. Write as much data as you can (before EWOULDBLOCK is returned).
3. Re-enable notifier if you have more data to write.

On Windows, CopperSpice always disables the notifier after getting a notification, and only re-enables it if more data is expected. For example, if data is read from the socket and it can be used to read more, or if reading or writing is not possible because the socket would block, in which case it is necessary to wait before attempting to read or write again.

See also

QFile, QProcess, QTcpSocket, QUdpSocket