QLocalSocket Class ReferenceThe QLocalSocket class provides a local socket. More... #include <QLocalSocket> Inherits: QIODevice. This class was introduced in Qt 4.4. Public Types
Public Functions
Reimplemented Public Functions
Signals
Reimplemented Protected Functions
Additional Inherited Members
Detailed DescriptionThe QLocalSocket class provides a local socket. On Windows this is a named pipe and on Unix this is a local domain socket. If an error occurs, socketError() returns the type of error, and errorString() can be called to get a human readable description of what happened. Although QLocalSocket is designed for use with an event loop, it's possible to use it without one. In that case, you must use waitForConnected(), waitForReadyRead(), waitForBytesWritten(), and waitForDisconnected() which blocks until the operation is complete or the timeout expires. Note that this feature is not supported on versions of Windows earlier than Windows XP. See also QLocalServer. Member Type Documentation
|
Constant | Value | Description |
---|---|---|
QLocalSocket::ConnectionRefusedError | QAbstractSocket::ConnectionRefusedError | The connection was refused by the peer (or timed out). |
QLocalSocket::PeerClosedError | QAbstractSocket::RemoteHostClosedError | The remote socket closed the connection. Note that the client socket (i.e., this socket) will be closed after the remote close notification has been sent. |
QLocalSocket::ServerNotFoundError | QAbstractSocket::HostNotFoundError | The local socket name was not found. |
QLocalSocket::SocketAccessError | QAbstractSocket::SocketAccessError | The socket operation failed because the application lacked the required privileges. |
QLocalSocket::SocketResourceError | QAbstractSocket::SocketResourceError | The local system ran out of resources (e.g., too many sockets). |
QLocalSocket::SocketTimeoutError | QAbstractSocket::SocketTimeoutError | The socket operation timed out. |
QLocalSocket::DatagramTooLargeError | QAbstractSocket::DatagramTooLargeError | The datagram was larger than the operating system's limit (which can be as low as 8192 bytes). |
QLocalSocket::ConnectionError | QAbstractSocket::NetworkError | An error occurred with the connection. |
QLocalSocket::UnsupportedSocketOperationError | QAbstractSocket::UnsupportedSocketOperationError | The requested socket operation is not supported by the local operating system. |
QLocalSocket::UnknownSocketError | QAbstractSocket::UnknownSocketError | An unidentified error occurred. |
This enum describes the different states in which a socket can be.
Constant | Value | Description |
---|---|---|
QLocalSocket::UnconnectedState | QAbstractSocket::UnconnectedState | The socket is not connected. |
QLocalSocket::ConnectingState | QAbstractSocket::ConnectingState | The socket has started establishing a connection. |
QLocalSocket::ConnectedState | QAbstractSocket::ConnectedState | A connection is established. |
QLocalSocket::ClosingState | QAbstractSocket::ClosingState | The socket is about to close (data may still be waiting to be written). |
See also QLocalSocket::state().
Creates a new local socket. The parent argument is passed to QObject's constructor.
Destroys the socket, closing the connection if necessary.
Aborts the current connection and resets the socket. Unlike disconnectFromServer(), this function immediately closes the socket, clearing any pending data in the write buffer.
See also disconnectFromServer() and close().
Reimplemented from QIODevice::bytesAvailable().
Reimplemented from QIODevice::bytesToWrite().
Reimplemented from QIODevice::canReadLine().
Reimplemented from QIODevice::close().
Attempts to make a connection to name.
The socket is opened in the given openMode and first enters ConnectingState. It then attempts to connect to the address or addresses returned by the lookup. Finally, if a connection is established, QLocalSocket enters ConnectedState and emits connected().
At any point, the socket can emit error() to signal that an error occurred.
See also state(), serverName(), and waitForConnected().
This signal is emitted after connectToServer() has been called and a connection has been successfully established.
See also connectToServer() and disconnected().
Attempts to close the socket. If there is pending data waiting to be written, QLocalSocket will enter ClosingState and wait until all data has been written. Eventually, it will enter UnconnectedState and emit the disconnectedFromServer() signal.
See also connectToServer().
This signal is emitted when the socket has been disconnected.
See also connectToServer(), disconnectFromServer(), abort(), and connected().
Returns the type of error that last occurred.
See also state() and errorString().
This signal is emitted after an error occurred. The socketError parameter describes the type of error that occurred.
QLocalSocket::LocalSocketError is not a registered metatype, so for queued connections, you will have to register it with Q_DECLARE_METATYPE() and qRegisterMetaType().
See also error(), errorString(), and Creating Custom Qt Types.
This function writes as much as possible from the internal write buffer to the socket, without blocking. If any data was written, this function returns true; otherwise false is returned.
Call this function if you need QLocalSocket to start sending buffered data immediately. The number of bytes successfully written depends on the operating system. In most cases, you do not need to call this function, because QLocalSocket will start sending data automatically once control goes back to the event loop. In the absence of an event loop, call waitForBytesWritten() instead.
See also write() and waitForBytesWritten().
Returns the server path that the socket is connected to.
Note: The return value of this function is platform specific.
See also connectToServer() and serverName().
Reimplemented from QIODevice::isSequential().
Returns true if the socket is valid and ready for use; otherwise returns false.
Note: The socket's state must be ConnectedState before reading and writing can occur.
See also state() and connectToServer().
Returns the size of the internal read buffer. This limits the amount of data that the client can receive before you call read() or readAll(). A read buffer size of 0 (the default) means that the buffer has no size limit, ensuring that no data is lost.
See also setReadBufferSize() and read().
Reimplemented from QIODevice::readData().
Returns the name of the peer as specified by connectToServer(), or an empty QString if connectToServer() has not been called or it failed.
See also connectToServer() and fullServerName().
Sets the size of QLocalSocket's internal read buffer to be size bytes.
If the buffer size is limited to a certain size, QLocalSocket won't buffer more than this size of data. Exceptionally, a buffer size of 0 means that the read buffer is unlimited and all incoming data is buffered. This is the default.
This option is useful if you only read the data at certain points in time (e.g., in a real-time streaming application) or if you want to protect your socket against receiving too much data, which may eventually cause your application to run out of memory.
See also readBufferSize() and read().
Initializes QLocalSocket with the native socket descriptor socketDescriptor. Returns true if socketDescriptor is accepted as a valid socket descriptor; otherwise returns false. The socket is opened in the mode specified by openMode, and enters the socket state specified by socketState.
Note: It is not possible to initialize two local sockets with the same native socket descriptor.
See also socketDescriptor(), state(), and openMode().
Returns the native socket descriptor of the QLocalSocket object if this is available; otherwise returns -1.
The socket descriptor is not available when QLocalSocket is in UnconnectedState.
See also setSocketDescriptor().
Returns the state of the socket.
See also error().
This signal is emitted whenever QLocalSocket's state changes. The socketState parameter is the new state.
QLocalSocket::SocketState is not a registered metatype, so for queued connections, you will have to register it with Q_DECLARE_METATYPE() and qRegisterMetaType().
See also state() and Creating Custom Qt Types.
Reimplemented from QIODevice::waitForBytesWritten().
Waits until the socket is connected, up to msecs milliseconds. If the connection has been established, this function returns true; otherwise it returns false. In the case where it returns false, you can call error() to determine the cause of the error.
The following example waits up to one second for a connection to be established:
socket->connectToServer("market"); if (socket->waitForConnected(1000)) qDebug("Connected!");
If msecs is -1, this function will not time out.
See also connectToServer() and connected().
Waits until the socket has disconnected, up to msecs milliseconds. If the connection has been disconnected, this function returns true; otherwise it returns false. In the case where it returns false, you can call error() to determine the cause of the error.
The following example waits up to one second for a connection to be closed:
socket->disconnectFromServer(); if (socket->waitForDisconnected(1000)) qDebug("Disconnected!");
If msecs is -1, this function will not time out.
See also disconnectFromServer() and close().
Reimplemented from QIODevice::waitForReadyRead().
This function blocks until data is available for reading and the readyRead() signal has been emitted. The function will timeout after msecs milliseconds; the default timeout is 30000 milliseconds.
The function returns true if data is available for reading; otherwise it returns false (if an error occurred or the operation timed out).
See also waitForBytesWritten().
Reimplemented from QIODevice::writeData().