The QSocketDevice class provides a platform-independent low-level socket API.
.PP
This class provides a low level API for working with sockets. Users of this class are assumed to have networking experience. For most users the QSocket class provides a much easier and high level alternative, but certain things (like UDP) can't be done with QSocket and if you need a platform-independent API for those, QSocketDevice is the right choice.
When calling connect() or bind(), QSocketDevice detects the protocol family (IPv4, IPv6) automatically. Passing the protocol family to QSocketDevice's constructor or to setSocket() forces creation of a socket device of a specific protocol. If not set, the protocol will be detected at the first call to connect() or bind().
.PP
See also QSocket, QSocketNotifier, QHostAddress, and Input/Output and Networking.
.SS "Member Type Documentation"
.SH "QSocketDevice::Error"
This enum type describes the error states of QSocketDevice.
.TP
\fCQSocketDevice::NoError\fR - No error has occurred.
.TP
\fCQSocketDevice::AlreadyBound\fR - The device is already bound, according to bind().
.TP
\fCQSocketDevice::Inaccessible\fR - The operating system or firewall prohibited the action.
.TP
\fCQSocketDevice::NoResources\fR - The operating system ran out of a resource.
.TP
\fCQSocketDevice::InternalError\fR - An internal error occurred in QSocketDevice.
.TP
\fCQSocketDevice::Impossible\fR - An attempt was made to do something which makes no sense. For example:
.IP
.nf
.br
::close( sd->socket() );
.br
sd->writeBlock( someData, 42 );
.br
.fi
The libc ::close() closes the socket, but QSocketDevice is not aware of this. So when you call writeBlock(), the impossible happens.
.TP
\fCQSocketDevice::NoFiles\fR - The operating system will not let QSocketDevice open another file.
.TP
\fCQSocketDevice::ConnectionRefused\fR - A connection attempt was rejected by the peer.
.TP
\fCQSocketDevice::NetworkFailure\fR - There is a network failure.
.TP
\fCQSocketDevice::UnknownError\fR - The operating system did something unexpected.
.SH "QSocketDevice::Protocol"
This enum type describes the protocol family of the socket. Possible values are:
.TP
\fCQSocketDevice::IPv4\fR - The socket is an IPv4 socket.
.TP
\fCQSocketDevice::IPv6\fR - The socket is an IPv6 socket.
.TP
\fCQSocketDevice::Unknown\fR - The protocol family of the socket is not known. This can happen if you use QSocketDevice with an already existing socket; it tries to determine the protocol family, but this can fail if the protocol family is not known to QSocketDevice.
.PP
See also protocol() and setSocket().
.SH "QSocketDevice::Type"
This enum type describes the type of the socket:
.TP
\fCQSocketDevice::Stream\fR - a stream socket (TCP, usually)
.TP
\fCQSocketDevice::Datagram\fR - a datagram socket (UDP, usually)
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QSocketDevice::QSocketDevice ( Type type = Stream )"
Creates a QSocketDevice object for a stream or datagram socket.
.PP
The \fItype\fR argument must be either QSocketDevice::Stream for a reliable, connection-oriented TCP socket, or QSocketDevice::Datagram for an unreliable UDP socket.
.PP
The socket is created as an IPv4 socket.
.PP
See also blocking() and protocol().
.SH "QSocketDevice::QSocketDevice ( Type type, Protocol protocol, int dummy )"
Creates a QSocketDevice object for a stream or datagram socket.
.PP
The \fItype\fR argument must be either QSocketDevice::Stream for a reliable, connection-oriented TCP socket, or QSocketDevice::Datagram for an unreliable UDP socket.
.PP
The \fIprotocol\fR indicates whether the socket should be of type IPv4 or IPv6. Passing Unknown is not meaningful in this context and you should avoid using (it creates an IPv4 socket, but your code is not easily readable).
.PP
The argument \fIdummy\fR is necessary for compatibility with some compilers.
.PP
See also blocking() and protocol().
.SH "QSocketDevice::QSocketDevice ( int socket, Type type )"
Creates a QSocketDevice object for the existing socket \fIsocket\fR.
.PP
The \fItype\fR argument must match the actual socket type; use QSocketDevice::Stream for a reliable, connection-oriented TCP socket, or QSocketDevice::Datagram for an unreliable, connectionless UDP socket.
Extracts the first connection from the queue of pending connections for this socket and returns a new socket identifier. Returns -1 if the operation failed.
Assigns a name to an unnamed socket. The name is the host address \fIaddress\fR and the port number \fIport\fR. If the operation succeeds, bind() returns TRUE; otherwise it returns FALSE without changing what port() and address() return.
.PP
bind() is used by servers for setting up incoming connections. Call bind() before listen().
.SH "bool QSocketDevice::blocking () const"
Returns TRUE if the socket is valid and in blocking mode; otherwise returns FALSE.
.PP
Note that this function does not set error().
.PP
\fBWarning:\fR On Windows, this function always returns TRUE since the ioctlsocket() function is broken.
Returns the number of bytes available for reading, or -1 if an error occurred.
.PP
\fBWarning:\fR On Microsoft Windows, we use the ioctlsocket() function to determine the number of bytes queued on the socket. According to Microsoft (KB Q125486), ioctlsocket() sometimes returns an incorrect number. The only safe way to determine the amount of data on the socket is to read it using readBlock(). QSocket has workarounds to deal with this problem.
Connects to the IP address and port specified by \fIaddr\fR and \fIport\fR. Returns TRUE if it establishes a connection; otherwise returns FALSE. If it returns FALSE, error() explains why.
.PP
Note that error() commonly returns NoError for non-blocking sockets; this just means that you can call connect() again in a little while and it'll probably succeed.
.SH "Error QSocketDevice::error () const"
Returns the first error seen.
.SH "bool QSocketDevice::isValid () const"
Returns TRUE if this is a valid socket; otherwise returns FALSE.
.PP
See also socket().
.SH "bool QSocketDevice::listen ( int backlog )\fC [virtual]\fR"
Specifies how many pending connections a server socket can have. Returns TRUE if the operation was successful; otherwise returns FALSE. A \fIbacklog\fR value of 50 is quite common.
The listen() call only applies to sockets where type() is Stream, i.e. not to Datagram sockets. listen() must not be called before bind() or after accept().
Returns the address of the port this socket device is connected to. This may be 0.0.0.0 for a while, but is set to something sensible as soon as a sensible value is available.
.PP
Note that for Datagram sockets, this is the source port of the last packet received.
Returns the port number of the port this socket device is connected to. This may be 0 for a while, but is set to something sensible as soon as a sensible value is available.
.PP
Note that for Datagram sockets, this is the source port of the last packet received, and that it is in native byte order.
Returns the socket's protocol family, which is one of Unknown, IPv4, or IPv6.
.PP
QSocketDevice either creates a socket with a well known protocol family or it uses an already existing socket. In the first case, this function returns the protocol family it was constructed with. In the second case, it tries to determine the protocol family of the socket; if this fails, it returns Unknown.
Reads \fImaxlen\fR bytes from the socket into \fIdata\fR and returns the number of bytes read. Returns -1 if an error occurred. Returning 0 is not an error. For Stream sockets, 0 is returned when the remote host closes the connection. For Datagram sockets, 0 is a valid datagram size.
Sets the address of this socket to be usable by other sockets too if \fIenable\fR is TRUE, and to be used exclusively by this socket if \fIenable\fR is FALSE.
.PP
When a socket is reusable, other sockets can use the same port number (and IP address), which is generally useful. Of course other sockets cannot use the same (address,port,peer-address,peer-port) 4-tuple as this socket, so there is no risk of confusing the two TCP connections.
Makes the socket blocking if \fIenable\fR is TRUE or nonblocking if \fIenable\fR is FALSE.
.PP
Sockets are blocking by default, but we recommend using nonblocking socket operations, especially for GUI programs that need to be responsive.
.PP
\fBWarning:\fR On Windows, this function should be used with care since whenever you use a QSocketNotifier on Windows, the socket is immediately made nonblocking.
Sets the size of the operating system receive buffer to \fIsize\fR.
.PP
The operating system receive buffer size effectively limits two things: how much data can be in transit at any one moment, and how much data can be received in one iteration of the main event loop.
.PP
The default is operating system-dependent. A socket that receives large amounts of data is probably best with a buffer size of 49152.
Sets the size of the operating system send buffer to \fIsize\fR.
.PP
The operating system send buffer size effectively limits how much data can be in transit at any one moment.
.PP
The default is operating system-dependent. A socket that sends large amounts of data is probably best with a buffer size of 49152.
.SH "void QSocketDevice::setSocket ( int socket, Type type )\fC [virtual]\fR"
Sets the socket device to operate on the existing socket \fIsocket\fR.
.PP
The \fItype\fR argument must match the actual socket type; use QSocketDevice::Stream for a reliable, connection-oriented TCP socket, or QSocketDevice::Datagram for an unreliable, connectionless UDP socket.
.PP
Any existing socket is closed.
.PP
See also isValid() and close().
.SH "int QSocketDevice::socket () const"
Returns the socket number, or -1 if it is an invalid socket.
.PP
See also isValid() and type().
.SH "Type QSocketDevice::type () const"
Returns the socket type which is either QSocketDevice::Stream or QSocketDevice::Datagram.
Wait up to \fImsecs\fR milliseconds for more data to be available. If \fImsecs\fR is -1 the call will block indefinitely.
.PP
Returns the number of bytes available for reading, or -1 if an error occurred.
.PP
If \fItimeout\fR is non-null and no error occurred (i.e. it does not return -1): this function sets \fI*timeout\fR to TRUE, if the reason for returning was that the timeout was reached; otherwise it sets \fI*timeout\fR to FALSE. This is useful to find out if the peer closed the connection.
.PP
\fBWarning:\fR This is a blocking call and should be avoided in event driven applications.
