|
|
int |
#include <dcopglobal.h>
DCOP Protocol description ================
A DCOPSend message does not expect any reply. data: << fromId << toId << objId << fun << dataSize + data[dataSize]
A DCOPCall message can get a DCOPReply, a DCOPReplyFailed or a DCOPReplyWait message in response. data: << fromId << toId << objId << fun << dataSize + data[dataSize]
DCOPReply is the successfull reply to a DCOPCall message data: << replyType << replyDataSize + replyData[replyDataSize]
DCOPReplyFailed indicates failure of a DCOPCall message data:
DCOPReplyWait indicates that a DCOPCall message is succesfully being processed but that response will come later. data: << transactionId
DCOPReplyDelayed is the successfull reply to a DCOPCall message after a DCOPReplyWait message. data: << fromId << toId << transactionId << replyType << replyData
All c-strings (fromId, toId, objId, fun and replyType), are marshalled with their respective length as 32 bit unsigned integer first: data: length + string[length] Note: This happens automatically when using QCString on a QDataStream.
QDataStream& |
#include <dcopref.h>
Writes the reference (NOT the object itself) to the stream.
QDataStream& |
#include <dcopref.h>
Reads a reference from the stream.
Generated by: root@porky.devel.redhat.com on Wed May 10 08:56:33 2000, using kdoc 2.0a35. |