DCOPClient Class Reference
Inter-process communication and remote procedure calls for KDE applications. More...
#include <dcopclient.h>
Inheritance diagram for DCOPClient:

Signals | |
void | applicationRegistered (const QCString &appId) |
void | applicationRemoved (const QCString &appId) |
void | attachFailed (const QString &msg) |
void | blockUserInput (bool block) |
void | callBack (int, const QCString &, const QByteArray &) |
Public Methods | |
DCOPClient () | |
virtual | ~DCOPClient () |
bool | attach () |
void | bindToApp () |
bool | detach () |
bool | isAttached () const |
bool | isAttachedToForeignServer () const |
bool | acceptCalls () const |
void | setAcceptCalls (bool b) |
bool | qtBridgeEnabled () |
void | setQtBridgeEnabled (bool b) |
QCString | registerAs (const QCString &appId, bool addPID=true) |
bool | isRegistered () const |
QCString | appId () const |
int | socket () const |
void | suspend () |
void | resume () |
bool | isSuspended () const |
bool | send (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QByteArray &data) |
bool | send (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QString &data) |
bool | call (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QByteArray &data, QCString &replyType, QByteArray &replyData, bool useEventLoop, int timeout) |
bool | call (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QByteArray &data, QCString &replyType, QByteArray &replyData, bool useEventLoop=false) |
int | callAsync (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QByteArray &data, QObject *callBackObj, const char *callBackSlot) |
bool | findObject (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QByteArray &data, QCString &foundApp, QCString &foundObj, bool useEventLoop, int timeout) |
bool | findObject (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QByteArray &data, QCString &foundApp, QCString &foundObj, bool useEventLoop=false) |
void | emitDCOPSignal (const QCString &object, const QCString &signal, const QByteArray &data) |
void | emitDCOPSignal (const QCString &signal, const QByteArray &data) |
bool | connectDCOPSignal (const QCString &sender, const QCString &senderObj, const QCString &signal, const QCString &receiverObj, const QCString &slot, bool Volatile) |
bool | connectDCOPSignal (const QCString &sender, const QCString &signal, const QCString &receiverObj, const QCString &slot, bool Volatile) KDE_DEPRECATED |
bool | disconnectDCOPSignal (const QCString &sender, const QCString &senderObj, const QCString &signal, const QCString &receiverObj, const QCString &slot) |
bool | disconnectDCOPSignal (const QCString &sender, const QCString &signal, const QCString &receiverObj, const QCString &slot) KDE_DEPRECATED |
virtual bool | process (const QCString &fun, const QByteArray &data, QCString &replyType, QByteArray &replyData) |
DCOPClientTransaction * | beginTransaction () |
void | endTransaction (DCOPClientTransaction *t, QCString &replyType, QByteArray &replyData) |
Q_INT32 | transactionId () const |
bool | isApplicationRegistered (const QCString &remApp) |
QCStringList | registeredApplications () |
QCStringList | remoteObjects (const QCString &remApp, bool *ok=0) |
QCStringList | remoteInterfaces (const QCString &remApp, const QCString &remObj, bool *ok=0) |
QCStringList | remoteFunctions (const QCString &remApp, const QCString &remObj, bool *ok=0) |
bool | receive (const QCString &app, const QCString &obj, const QCString &fun, const QByteArray &data, QCString &replyType, QByteArray &replyData) |
bool | find (const QCString &app, const QCString &obj, const QCString &fun, const QByteArray &data, QCString &replyType, QByteArray &replyData) |
QCString | senderId () const |
void | setDefaultObject (const QCString &objId) |
QCString | defaultObject () const |
void | setNotifications (bool enabled) |
void | setDaemonMode (bool daemonMode) |
void | setPriorityCall (bool) |
void | handleAsyncReply (ReplyStruct *replyStruct) |
Static Public Methods | |
void | setServerAddress (const QCString &addr) |
QCString | normalizeFunctionSignature (const QCString &fun) |
DCOPClient * | mainClient () |
void | setMainClient (DCOPClient *mainClient) |
DCOPClient * | findLocalClient (const QCString &_appId) |
void | emergencyClose () |
const char * | postMortemSender () |
const char * | postMortemObject () |
const char * | postMortemFunction () |
QCString | dcopServerFile (const QCString &hostname=0) |
QCString | dcopServerFileOld (const QCString &hostname=0) KDE_DEPRECATED |
QCString | iceauthPath () |
Protected Slots | |
void | processSocketData (int socknum) |
Protected Methods | |
virtual void | virtual_hook (int id, void *data) |
Related Functions | |
(Note that these are not member functions.) | |
Bool | dcop_attach (void) |
char * | dcop_register (const char *app_name, Bool add_pid) |
Bool | dcop_detach (void) |
Bool | dcop_register_callback (const char *object_id, dcop_callback_t callback) |
Bool | dcop_send_signal (const char *receiving_app, const char *object, const char *function, char *data, int data_length) |
Bool | dcop_call (const char *app_name, const char *remote_app_name, const char *remote_object_id, const char *remote_function, const char *data, int data_length, char **reply_type, char **reply_data, int *reply_data_length) |
Detailed Description
Inter-process communication and remote procedure calls for KDE applications.This class provides IPC and RPC for KDE applications. Usually you will not have to instantiate one yourself because KApplication contains a method to return a pointer to a DCOPClient object which can be used for your whole application.
Before being able to send or receive any DCOP messages, you will have to attach your client object to the DCOP server, and then register your application with a specific name. See attach() and registerAs() for more information.
Data to be sent should be serialized into a QDataStream which was initialized with the QByteArray that you actually intend to send the data in. An example of how you might do this:
QByteArray data; QDataStream arg(data, IO_WriteOnly); arg << QString("This is text I am serializing"); client->send("someApp", "someObject", "someFunction(QString)", data);
- See also:
- KApplication::dcopClient()
- Author:
- Preston Brown <pbrown@kde.org>, Matthias Ettrich <ettrich@kde.org>
Definition at line 68 of file dcopclient.h.
Constructor & Destructor Documentation
|
Constructs a new DCOP client, but does not attach to any server.
Definition at line 582 of file dcopclient.cpp. References QObject::connect(), mainClient(), and setMainClient(). |
|
Cleans up any open connections and dynamic data.
Definition at line 606 of file dcopclient.cpp. References detach(), mainClient(), and setMainClient(). |
Member Function Documentation
|
Sets the address of a server to use upon attaching. If no server address is ever specified, attach will try its best to find the server anyway.
Definition at line 623 of file dcopclient.cpp. |
|
Attaches to the DCOP server. If the connection was already attached, the connection will be re-established with the current server address. Naturally, only attached application can use DCOP services. If a QApplication object exists then client registers itself as QApplication::name() + "-" + <pid>. If no QApplication object exists the client registers itself as "anonymous". If you want to register differently, you should use registerAs() instead.
Definition at line 631 of file dcopclient.cpp. |
|
Detaches from the DCOP server.
Definition at line 842 of file dcopclient.cpp. Referenced by processSocketData(), registerAs(), and ~DCOPClient(). |
|
Returns whether or not the client is attached to the server.
Definition at line 865 of file dcopclient.cpp. Referenced by acceptCalls(), endTransaction(), isAttachedToForeignServer(), registerAs(), and send(). |
|
Returns whether the client is attached to a server owned by another user.
Definition at line 873 of file dcopclient.cpp. References isAttached(). |
|
Returns whether the client handles incoming calls.
Definition at line 878 of file dcopclient.cpp. References isAttached(). |
|
Specify whether the client should accept incoming calls. By default clients accept incoming calls, but not when connected to a foreign server.
Definition at line 883 of file dcopclient.cpp. |
|
Returns whether the DCOP - Qt bridge is enabled. By default the DCOP - Qt bridge is enabled.
Definition at line 889 of file dcopclient.cpp. |
|
Specify whether Qt objects of the application should be accessible via DCOP. By default the DCOP - Qt bridge is enabled.
Definition at line 894 of file dcopclient.cpp. |
|
Registers at the DCOP server. If the application was already registered, the registration will be re-done with the new appId.
Registration is necessary if you want to allow other clients to talk to you. They can do so using your
Definition at line 899 of file dcopclient.cpp. References call(), detach(), isAttached(), QCString::isNull(), isRegistered(), and QCString::sprintf(). |
|
Returns whether or not the client is registered at the server.
Definition at line 946 of file dcopclient.cpp. Referenced by registerAs(). |
|
Returns the current app id or a null string if the application hasn't yet been registered.
Definition at line 952 of file dcopclient.cpp. |
|
Returns the socket fd that is used for communication with the server.
Definition at line 958 of file dcopclient.cpp. |
|
Temporarily suspends processing of DCOP events. This can be useful if you need to show e.g. a dialog before your application is ready to accept DCOP requests. Normally the dialog would start an event loop and in this event loop DCOP requests will be handled. Be aware that not responding to DCOP requests may cause other programs that want to communicate with your application, to hang.
Definition at line 653 of file dcopclient.cpp. |
|
Resumes the processing of DCOP events.
Definition at line 659 of file dcopclient.cpp. |
|
Returns whether DCOP events are being processed.
Definition at line 665 of file dcopclient.cpp. |
|
Sends a data block to the server.
Definition at line 1006 of file dcopclient.cpp. References findLocalClient(), isAttached(), QCString::isEmpty(), normalizeFunctionSignature(), and receive(). Referenced by emitDCOPSignal(), and send(). |
|
This function acts exactly the same as the above, but the data parameter can be specified as a QString for convenience.
Definition at line 1061 of file dcopclient.cpp. References send(). |
|
Performs a synchronous send and receive. The parameters are the same as for send, with the exception of another QByteArray being provided for results to be (optionally) returned in. A call blocks the application until the process receives the answer.
If
Definition at line 1695 of file dcopclient.cpp. References QApplication::eventLoop(), findLocalClient(), QCString::isEmpty(), isLocalTransactionFinished(), receive(), and transactionId(). Referenced by call(), connectDCOPSignal(), disconnectDCOPSignal(), isApplicationRegistered(), registerAs(), registeredApplications(), remoteFunctions(), remoteInterfaces(), remoteObjects(), setDaemonMode(), and setNotifications(). |
|
Definition at line 1687 of file dcopclient.cpp. References call(). |
|
Performs a asynchronous send with receive callback. The first four parameters are the same as for send.
The slot should have the following signature: callBackSlot(int callId, const QCString& replyType, const QByteArray &replyData);
Definition at line 1739 of file dcopclient.cpp. References QTimer::singleShot(). |
|
Searches for an object which matches a criteria.
findObject calls
If A findObject blocks the application until the process receives the answer.
If
Definition at line 1078 of file dcopclient.cpp. References DCOPRef::app(), QValueList< QCString >::append(), QValueList< QCString >::begin(), QValueList< QCString >::end(), QApplication::eventLoop(), find(), findLocalClient(), QCString::isEmpty(), isLocalTransactionFinished(), QCString::length(), DCOPRef::object(), registeredApplications(), and transactionId(). Referenced by findObject(). |
|
Definition at line 1070 of file dcopclient.cpp. References findObject(). |
|
Emits
Definition at line 2061 of file dcopclient.cpp. References normalizeFunctionSignature(), and send(). Referenced by DCOPObject::emitDCOPSignal(). |
|
Connects to a DCOP signal.
Definition at line 2074 of file dcopclient.cpp. References call(), and normalizeFunctionSignature(). Referenced by DCOPObject::connectDCOPSignal(), and connectDCOPSignal(). |
|
Definition at line 2102 of file dcopclient.cpp. References connectDCOPSignal(). |
|
Disconnects a DCOP signal.
A special case is when both
Definition at line 2109 of file dcopclient.cpp. References call(), and normalizeFunctionSignature(). Referenced by DCOPObject::disconnectDCOPSignal(), disconnectDCOPSignal(), DCOPObject::setObjId(), and DCOPObject::~DCOPObject(). |
|
Definition at line 2136 of file dcopclient.cpp. References disconnectDCOPSignal(). |
|
Reimplement this function to handle app-wide function calls unassociated w/an object.
Note that If you do not want to reimplement this function for whatever reason, you can also use a default object or a DCOPObjectProxy.
Definition at line 1174 of file dcopclient.cpp. |
|
Delays the reply of the current function call until endTransaction() is called. This allows a server to queue requests. Note: Should be called from inside process() only!
Definition at line 1980 of file dcopclient.cpp. |
|
Sends the delayed reply of a function call.
Definition at line 2010 of file dcopclient.cpp. References isAttached(). |
|
Test whether the current function call is delayed. Note: Should be called from inside process() only!
Definition at line 2001 of file dcopclient.cpp. Referenced by call(), and findObject(). |
|
Checks whether
Definition at line 1180 of file dcopclient.cpp. References call(). |
|
Retrieves the list of all currently registered applications from dcopserver.
Definition at line 1194 of file dcopclient.cpp. References call(). Referenced by findObject(). |
|
Retrieves the list of objects of the remote application
Definition at line 1206 of file dcopclient.cpp. References call(). |
|
Retrieves the list of interfaces of the remote object
Definition at line 1222 of file dcopclient.cpp. References call(). |
|
Retrieves the list of functions of the remote object
Definition at line 1238 of file dcopclient.cpp. References call(). |
|
Normalizes the function signature A normalized signature doesn't contain any unnecessary whitespace anymore. The remaining whitespace consists of single blanks only (0x20). Example for a normalized signature: "someFunction(QString,int)" When using send() or call(), normalization is done automatically for you.
Definition at line 972 of file dcopclient.cpp. References QCString::copy(), QCString::isEmpty(), and QCString::resize(). Referenced by connectDCOPSignal(), disconnectDCOPSignal(), emitDCOPSignal(), and send(). |
|
Returns the appId of the last application that talked to us.
Definition at line 1000 of file dcopclient.cpp. |
|
Installs object
All app-wide messages that have not been processed by the dcopclient will be send further to
Definition at line 1954 of file dcopclient.cpp. |
|
Returns the current default object or an empty string if no object is installed as default object. A default object receives application-wide messages that have not been processed by the DCOPClient itself.
Definition at line 1960 of file dcopclient.cpp. |
|
Enables / disables the applicationRegistered() / applicationRemoved() signals.
Note that a counter is maintained about how often this method was called. If this method is called twice with They are disabled by default.
Definition at line 1254 of file dcopclient.cpp. References call(). |
|
Tells the dcopserver to treat the client as daemon client, not as regular client. If the number of regular clients drops down to zero, the dcopserver will emit a KDE termination signal after 10 seconds.
Definition at line 1266 of file dcopclient.cpp. References call(). |
|
Returns the application's main dcop client. The main client can be used by objects that do not have any specific access to a dcop client. In KDE applications, the main client usually is the same as KApplication::dcopClient().
Definition at line 571 of file dcopclient.cpp. Referenced by DCOPObject::connectDCOPSignal(), DCOPStub::dcopClient(), DCOPRef::dcopClient(), DCOPClient(), DCOPObject::disconnectDCOPSignal(), DCOPObject::emitDCOPSignal(), DCOPObject::setObjId(), ~DCOPClient(), and DCOPObject::~DCOPObject(). |
|
Sets the application's main dcop client. The main client can be used by objects that do not have any specific access to a dcop client. In KDE applications, the main client usually is the same as KApplication::dcopClient().
Definition at line 576 of file dcopclient.cpp. Referenced by DCOPClient(), and ~DCOPClient(). |
|
Look for the given client only in this process. This can be used to check whether a given client (by name) is running in the same process or in another one. Definition at line 97 of file dcopclient.cpp. References QAsciiDict::find(). Referenced by call(), findObject(), and send(). |
|
File with information how to reach the dcopserver.
Definition at line 287 of file dcopclient.cpp. |
|
Definition at line 294 of file dcopclient.cpp. |
|
Return the path of iceauth or an empty string if not found.
Definition at line 210 of file dcopclient.cpp. References QCString::isEmpty(), and QCString::isNull(). |
|
Indicates that the application You need to call setNotifications() first, to tell the DCOP server that you want to get these events.
|
|
Indicates that the formerly registered application You need to call setNotifications() first, to tell the DCOP server that you want to get these events.
|
|
Indicates that the process of establishing DCOP communications failed in some manner. Usually attached to a dialog box or some other visual aid.
|
|
Indicates that user input shall be blocked or released, depending on the argument. The signal is emitted whenever the client has to wait too long (i.e. more than 1/10 of a second) for an answer to a synchronous call. In that case, it will enter a local event loop to keep the GUI updated until finally an answer arrives. In KDE, the KApplication object connects to this signal to be able to block any user input (i.e. mouse and key events) while we are waiting for an answer. If we did not do this, the application might end up in an illegal state, as a keyboard shortcut or a mouse action might cause another dcop call to be issued.
|
|
Process data from the socket.
Definition at line 1920 of file dcopclient.cpp. References detach(). |
The documentation for this class was generated from the following files: