KMessageIO
#include <KGame/KMessageIO>
Signals | |
void | connectionBroken () |
void | received (const QByteArray &msg) |
Public Slots | |
virtual void | send (const QByteArray &msg)=0 |
Protected Attributes | |
quint32 | m_id |
Detailed Description
This abstract base class represents one end of a message connections between two clients.
Each client has one object of a subclass of KMessageIO. Calling /e send() on one object will emit the signal /e received() on the other object, and vice versa.
For each type of connection (TCP/IP socket, COM port, direct connection within the same class) a subclass of KMessageIO must be defined that implements the pure virtual methods /e send() and /e isConnected(), and sends the signals. (See /e KMessageSocket for an example implementation.)
Two subclasses are already included: /e KMessageSocket (connection using TCP/IP sockets) and /e KMessageDirect (connection using method calls, both sides must be within the same process).
Definition at line 43 of file kmessageio.h.
Constructor & Destructor Documentation
◆ KMessageIO()
The usual QObject constructor, does nothing else.
Definition at line 23 of file kmessageio.cpp.
◆ ~KMessageIO()
|
override |
The usual destructor, does nothing special.
Definition at line 29 of file kmessageio.cpp.
Member Function Documentation
◆ connectionBroken
|
signal |
This signal is emitted when the connection is closed.
This can be caused by a hardware error (e.g. broken internet connection) or because the other object was killed.
Note: Sometimes a broken connection can be undetected for a long time, or may never be detected at all. So don't rely on this signal!
◆ id()
quint32 KMessageIO::id | ( | ) |
Queries the ID of this object.
Definition at line 38 of file kmessageio.cpp.
◆ isConnected()
|
virtual |
This method returns the status of the object, whether it is already (or still) connected to another KMessageIO object or not.
This is a pure virtual method, so it has to be implemented in a subclass of KMessageIO.
Reimplemented in KMessageSocket, and KMessageDirect.
Definition at line 49 of file kmessageio.cpp.
◆ isNetwork()
|
virtual |
- Returns
- Whether this KMessageIO is a network IO or not.
Reimplemented in KMessageSocket, and KMessageDirect.
Definition at line 43 of file kmessageio.cpp.
◆ peerName()
|
virtual |
- Returns
- "localhost" in the default implementation. Reimplemented in KMessageSocket
Reimplemented in KMessageSocket.
Definition at line 60 of file kmessageio.cpp.
◆ peerPort()
|
virtual |
- Returns
- 0 in the default implementation. Reimplemented in KMessageSocket.
Reimplemented in KMessageSocket.
Definition at line 55 of file kmessageio.cpp.
◆ received
|
signal |
This signal is emitted when /e send() on the connected KMessageIO object is called.
The parameter contains the same data array in /e msg as was used in /e send().
◆ rtti()
|
inlinevirtual |
The runtime identification.
Reimplemented in KMessageSocket, and KMessageDirect.
Definition at line 61 of file kmessageio.h.
◆ send
|
pure virtualslot |
This slot sends the data block in /e msg to the connected object, that will emit /e received().
For a concrete class, you have to subclass /e KMessageIO and overwrite this method. In the subclass, implement this method as an ordinary method, not as a slot! (Otherwise another slot would be defined. It would work, but uses more memory and time.) See /e KMessageSocket for an example implementation.
Implemented in KMessageSocket, and KMessageDirect.
◆ setId()
void KMessageIO::setId | ( | quint32 | id | ) |
Sets the ID number of this object.
This number can for example be used to distinguish several objects in a server.
NOTE: Sometimes it is useful to let two connected KMessageIO objects have the same ID number. You have to do so yourself, KMessageIO doesn't change this value on its own!
Definition at line 33 of file kmessageio.cpp.
Member Data Documentation
◆ m_id
|
protected |
Definition at line 139 of file kmessageio.h.
The documentation for this class was generated from the following files:
Documentation copyright © 1996-2024 The KDE developers.
Generated on Tue Mar 26 2024 11:16:50 by doxygen 1.10.0 written by Dimitri van Heesch, © 1997-2006
KDE's Doxygen guidelines are available online.