#include <ksock.h>
Public Slots | |
| void | slotWrite (int x) |
| void | slotRead (int x) |
Signals | |
| void | readEvent (KSocket *s) |
| void | writeEvent (KSocket *s) |
| void | closeEvent (KSocket *s) |
Public Methods | |
| KSocket (int _sock) | |
| KSocket (const char *_host, unsigned short int _port, int timeOut=30) | |
| KSocket (const char *_path) | |
| virtual | ~KSocket () |
| int | socket () const |
| void | enableRead (bool enable) |
| void | enableWrite (bool enable) |
You can connect this socket to any Internet address.
The socket gives you three signals: When ready for reading, ready for writing or if the connection is broken. Using socket() you get a file descriptor which you can use with the usual UNIX function like write() or read(). If you have already such a socket identifier you can construct a KSocket on this identifier.
If socket() delivers a value of -1 or less, the connection was not successful.
Definition at line 81 of file ksock.h.
|
|
Constructs a KSocket with the provided file descriptor.
|
|
||||||||||||||||
|
Creates a socket and connects to a host.
|
|
|
Connects to a UNIX domain socket.
|
|
|
Destructor. Closes the socket if it is still open. |
|
|
Raised when the connection is broken.
|
|
|
Enables the socket for reading. If you enable read mode, the socket will emit the signal readEvent() whenever there is something to read out of this socket.
|
|
|
Enables the socket for writing. If you enable write mode, the socket will emit the signal writeEvent() whenever the socket is ready for writing. Warning: If you forget to call enableWrite(false) when you are not ready to send data, you will get lots of writeEvent() signals, in the order of thousands a second !
|
|
|
Data has arrived for reading.
This signal will only be raised if enableRead(
|
|
|
Connected to the readNotifier. Called when the socket is ready for reading.
|
|
|
Connected to the writeNotifier. Called when the socket is ready for writing.
|
|
|
Returns a file descriptor for this socket.
|
|
|
Socket is ready for writing.
This signal will only be raised if enableWrite( Warning: If you forget to call enableWrite(false) when you are not ready to send data, you will get lots of writeEvent() signals, in the order of thousands a second !
|
1.2.18