Viadeo Twitter Google Bookmarks ! Facebook Digg del.icio.us MySpace Yahoo MyWeb Blinklist Netvouz Reddit Simpy StumbleUpon Bookmarks Windows Live Favorites 
Logo Documentation Qt ·  Page d'accueil  ·  Toutes les classes  ·  Classes principales  ·  Annotées  ·  Classes groupées  ·  Modules  ·  Fonctions  · 

QDBusConnectionInterface Class Reference
[QtDBus module]

The QDBusConnectionInterface class provides access to the D-Bus bus daemon service. More...

 #include <QDBusConnectionInterface>

Inherits QDBusAbstractInterface.

This class was introduced in Qt 4.2.

Public Types

Public Slots

  • QDBusReply<bool> isServiceRegistered ( const QString & serviceName ) const
  • QDBusReply<RegisterServiceReply> registerService ( const QString & serviceName, ServiceQueueOptions qoption = DontQueueService, ServiceReplacementOptions roption = DontAllowReplacement )
  • QDBusReply<QStringList> registeredServiceNames () const
  • QDBusReply<QString> serviceOwner ( const QString & name ) const
  • QDBusReply<uint> servicePid ( const QString & serviceName ) const
  • QDBusReply<uint> serviceUid ( const QString & serviceName ) const
  • QDBusReply<void> startService ( const QString & name )
  • QDBusReply<bool> unregisterService ( const QString & serviceName )
  • 1 public slot inherited from QObject

Signals

Additional Inherited Members


Detailed Description

The QDBusConnectionInterface class provides access to the D-Bus bus daemon service.

The D-BUS bus server daemon provides one special interface org.freedesktop.DBus that allows clients to access certain properties of the bus, such as the current list of clients connected. The QDBusConnectionInterface class provides access to that interface.

The most common uses of this class are to register and unregister service names on the bus using the registerService() and unregisterService() functions, query about existing names using the isServiceRegistered(), registeredServiceNames() and serviceOwner() functions, and to receive notification that a client has registered or de-registered through the serviceRegistered(), serviceUnregistered() and serviceOwnerChanged() signals.


Member Type Documentation

enum QDBusConnectionInterface::RegisterServiceReply

The possible return values from registerService():

ConstantValueDescription
QDBusConnectionInterface::ServiceNotRegistered0The call failed and the service name was not registered.
QDBusConnectionInterface::ServiceRegistered1The caller is now the owner of the service name.
QDBusConnectionInterface::ServiceQueued2The caller specified the QueueService flag and the service was already registered, so we are in queue.

The serviceRegistered() signal will be emitted when the service is acquired by this application.

enum QDBusConnectionInterface::ServiceQueueOptions

Flags for determining how a service registration should behave, in case the service name is already registered.

ConstantValueDescription
QDBusConnectionInterface::DontQueueService0If an application requests a name that is already owned, no queueing will be performed. The registeredService() call will simply fail. This is the default.
QDBusConnectionInterface::QueueService1Attempts to register the requested service, but do not try to replace it if another application already has it registered. Instead, simply put this application in queue, until it is given up. The serviceRegistered() signal will be emitted when that happens.
QDBusConnectionInterface::ReplaceExistingService2If another application already has the service name registered, attempt to replace it.

See also ServiceReplacementOptions.

enum QDBusConnectionInterface::ServiceReplacementOptions

Flags for determining if the D-BUS server should allow another application to replace a name that this application has registered with the ReplaceExistingService option.

The possible values are:

ConstantValueDescription
QDBusConnectionInterface::DontAllowReplacement0Do not allow another application to replace us. The service must be explicitly unregistered with unregisterService() for another application to acquire it. This is the default.
QDBusConnectionInterface::AllowReplacement1Allow other applications to replace us with the ReplaceExistingService option to registerService() without intervention. If that happens, the serviceUnregistered() signal will be emitted.

See also ServiceQueueOptions.


Member Function Documentation

QDBusReply<bool> QDBusConnectionInterface::isServiceRegistered ( const QString & serviceName ) const   [slot]

Returns true if the service name serviceName has is currently registered.

QDBusReply<RegisterServiceReply> QDBusConnectionInterface::registerService ( const QString & serviceName, ServiceQueueOptions qoption = DontQueueService, ServiceReplacementOptions roption = DontAllowReplacement )   [slot]

Requests to register the service name serviceName on the bus. The qoption flag specifies how the D-BUS server should behave if serviceName is already registered. The roption flag specifies if the server should allow another application to replace our registered name.

If the service registration succeeds, the serviceRegistered() signal will be emitted. If we are placed in queue, the signal will be emitted when we obtain the name. If roption is AllowReplacement, the serviceUnregistered() signal will be emitted if another application replaces this one.

See also unregisterService().

QDBusReply<QStringList> QDBusConnectionInterface::registeredServiceNames () const   [slot]

Lists all names currently registered on the bus.

QDBusReply<QString> QDBusConnectionInterface::serviceOwner ( const QString & name ) const   [slot]

Returns the unique connection name of the primary owner of the name name. If the requested name doesn't have an owner, returns a org.freedesktop.DBus.Error.NameHasNoOwner error.

void QDBusConnectionInterface::serviceOwnerChanged ( const QString & name, const QString & oldOwner, const QString & newOwner )   [signal]

This signal is emitted by the D-BUS server whenever a service ownership change happens in the bus, including apparition and disparition of names.

This signal means the application oldOwner lost ownership of bus name name to application newOwner. If oldOwner is an empty string, it means the name name has just been created; if newOwner is empty, the name name has no current owner and is no longer available.

QDBusReply<uint> QDBusConnectionInterface::servicePid ( const QString & serviceName ) const   [slot]

Returns the Unix Process ID (PID) for the process currently holding the bus service serviceName.

void QDBusConnectionInterface::serviceRegistered ( const QString & serviceName )   [signal]

This signal is emitted by the D-BUS server when the bus service name (unique connection name or well-known service name) given by serviceName is acquired by this application.

Acquisition happens after the application requested a name using registerService().

QDBusReply<uint> QDBusConnectionInterface::serviceUid ( const QString & serviceName ) const   [slot]

Returns the Unix User ID (UID) for the process currently holding the bus service serviceName.

void QDBusConnectionInterface::serviceUnregistered ( const QString & serviceName )   [signal]

This signal is emitted by the D-BUS server when the application loses ownership of the bus service name given by serviceName.

QDBusReply<void> QDBusConnectionInterface::startService ( const QString & name )   [slot]

Requests that the bus start the service given by the name name.

QDBusReply<bool> QDBusConnectionInterface::unregisterService ( const QString & serviceName )   [slot]

Releases the claim on the bus service name serviceName, that had been previously registered with registerService(). If this application had ownership of the name, it will be released for other applications to claim. If it only had the name queued, it gives up its position in the queue.

Publicité

Best Of

Actualités les plus lues

Semaine
Mois
Année
  1. « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 64
  2. Apercevoir la troisième dimension ou l'utilisation multithreadée d'OpenGL dans Qt, un article des Qt Quarterly traduit par Guillaume Belz 0
  3. Les développeurs ignorent-ils trop les failles découvertes dans leur code ? Prenez-vous en compte les remarques des autres ? 17
  4. BlackBerry 10 : premières images du prochain OS de RIM qui devrait intégrer des widgets et des tuiles inspirées de Windows Phone 0
  5. Quelles nouveautés de C++11 Visual C++ doit-il rapidement intégrer ? Donnez-nous votre avis 10
  6. Adieu qmake, bienvenue qbs : Qt Building Suite, un outil déclaratif et extensible pour la compilation de projets Qt 17
  7. La rubrique Qt a besoin de vous ! 1
Page suivante

Le Qt Developer Network au hasard

Logo

Comment fermer une application

Le Qt Developer Network est un réseau de développeurs Qt anglophone, où ils peuvent partager leur expérience sur le framework. Lire l'article.

Communauté

Ressources

Liens utiles

Contact

  • Vous souhaitez rejoindre la rédaction ou proposer un tutoriel, une traduction, une question... ? Postez dans le forum Contribuez ou contactez-nous par MP ou par email (voir en bas de page).

Qt dans le magazine

Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. Qt 4.2
Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD.
Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP !
 
 
 
 
Partenaires

Hébergement Web