The Qt Service Framework allows clients to discover and instantiate arbitrary services.
The QtMobility APIs are placed into the QtMobility namespace. This is done to facilitate the future migration of QtMobility APIs into Qt. See the Quickstart guide for an example on how the namespace impacts on application development.
The Qt Service Framework defines a unified way of finding, implementing and accessing services across multiple platforms.
Due to the service frameworks knowledge of service interfaces, their versions and QObject-based introspection it may even be used to unify and access multiple platform specific service implementations via the same Qt-based client application.
A service is an independent component that allows a client to perform a well-defined operation. Clients can find services based on their name and version as well as the interface that is implemented by the service object. Once the service has been identified the framework starts the service and returns a pointer to it. QServiceManager is the main interface through which clients can access the mentioned framework functionality. In addition services themselves may also act as clients to the service framework by requesting other services installed on the system.
Service provider are implemented via plug-ins. QServicePluginInterface defines the main interface for each plug-in. In order to avoid that clients have to link against service specific libraries each service object must be derived from QObject. Therefore the QMetaObject system can be used to dynamically discover and invoke the service's capabilities. To achieve the best level of access via the Qt meta object system services should be implemented in such a way that their entire functionality is accessible via the signals, slots, properties or invokable functions (see Q_INVOKABLE macro for more details).
Each service plug-in implements one service only but can provide multiple implementations for multiple interfaces. Therefore a service (plug-in) can retain a certain level of backwards compatibility even if the main service interface breaks in such a way that a new interface name has to be used. Existing clients can still use the previous version of service interface whereas new clients can utilize the new interface.
Services can also include remote processes. By registering with the service manager processes can communicate via signals, slots, invokable functions and properties as if they were local objects. Services can choose to be either shared between all clients, or unique to that client.
This section assumes that the user wants to access the FileStorage service which offers an implementation for the com.nokia.qt.examples.FileStorage interface The service framework enables multiple ways of accessing those implementations.
QServiceManager is the main class to lookup and instantiate services. Services can be found by constraining the search via service meta data or by using the default lookup mechanism.
The client code has precise knowledge of the service and its interfaces.
QServiceManager manager; QServiceFilter filter("com.nokia.qt.examples.FileStorage"); filter.setServiceName("FileStorage"); // find services complying with filter QList<QServiceInterfaceDescriptor> foundServices; foundServices = manager.findInterfaces(filter); Q_ASSERT(foundServices.count()); // instantiate the FileStorage object QObject *fileStorage; fileStorage = manager.loadInterface(foundServices.at(0));
It is assumed that the client has knowledge of the interface but does not really care about the specific type or version of the service implementing the interface. In such cases the default service lookup can be utilized to create a service object instance.
QServiceManager manager; manager.setInterfaceDefault("FileStorageService", "com.nokia.qt.examples.FileStorage");
The above call to QServiceManager::setInterfaceDefault() registers the FileStorageService as default implementation. Whenever a client asks for an implementation of com.nokia.qt.examples.FileStorage the FileStorageService service will be loaded. If (at the time of this call) the FileStorageService provides multiple registered implementations/versions for the same interface the latest version becomes the default. Therefore subsequent versions of the same interface must always be binary compatible to previous versions.
The current scope of the service manager object determines whether the default assignment is valid for all users or whether it is valid for the current user only. The system default is used if the user scope has not been defined. This enables users to customize their personal preferences. By default the first service installing a so far unknown interface becomes the system wide default selection.
This is the most common way of interacting with services.
storage = manager.loadInterface("com.nokia.qt.examples.FileStorage"); if (storage) QMetaObject::invokeMethod(storage, "deleteFile", Q_ARG(QString, "/tmp/readme.txt"));
The above invocation of the file storage object's deleteFile() function is done via the service's QMetaObject. The client does not require any knowledge of the objects actual type and therefore does not have to link against a service specific library.
So far all lookup mechanism returned a QObject pointer. This pointer can be utilized by introspecting the object, using Qt's meta object system. However in some use cases it may be more convenient to directly interact with the service object by including the service header and/or linking against the service provider. The main advantage is compile time checking. Its disadvantage is that client and service must share the implementation of the service object via a library they link against or via a common header file. Note that such sharing breaks the fundamental ServiceFramework principle of separating clients from service as changes of the service type may require changes to both, services and clients.
The subsequent code snippet demonstrates how this may look like:
#include <filestorage.h> ... QServiceManager manager; FileStorage *storage = 0; ... storage = manager.loadLocalTypedInterface<FileStorage>("com.nokia.qt.examples.FileStorage"); if (storage) storage->deleteFile("/tmp/readme.txt");
The QServiceManager operates in either User scope or System scope. By default, it operates in user scope. The choice of scope affects whether registered services are available system-wide or only to the current user, and whether service and interface lookups are limited to system-wide service or whether the current user's together with system service configurations are considered.
In user scope, services are registered in a storage location specific to the current user. When a default service is set for an interface using setInterfaceDefault(), the referenced service can be either a user-specific or system-wide service.
For service and interface lookups, a manager will first search the user-specific services; if the requested component is not found, the manager then searches the system-wide services, if the user has sufficient permissions to do so.
The QServiceManager::serviceAdded() and QServiceManager::serviceRemoved() notifications are emitted when services are added or removed from either the user-specific or system-wide services. These signals have a scope parameter to indicate the scope in which the service was added or removed. (Note the system-wide service notifications are only available if the user has sufficient permissions to access the system-wide service storage.)
In system scope, services are registered in a system-wide storage location. The manager does not access user-specific services for any operations. Service and interface lookups fail if the requested services are not found in the system-wide service storage. Service registration is performed in the system-wide storage.
If setInterfaceDefault() is called for a user-specific service, the operation fails.
Also, the QServiceManager::serviceAdded() and QServiceManager::serviceRemoved() notifications are only emitted for system-wide services.
New services can be installed and removed at runtime. An XML file is used to describe the service meta data and links the service code to its meta description.
Services are installed via an XML file which describes the meta data and location of the service. The XML file can be described via the following DTD:
<!ELEMENT SFW ( service ) > <!ATTLIST SFW version (1.0|1.1) #REQUIRED > <!ELEMENT service ( name, filepath | ipcaddress, description?, interface+ ) > <!ELEMENT description ( #CDATA ) > <!ELEMENT filepath ( #PCDATA ) > <!ELEMENT ipcaddress ( #PCDATA ) > <!ELEMENT interface ( name, version, description?, capabilities?, customproperty* ) > <!ELEMENT capabilities ( #PCDATA ) > <!ELEMENT name ( #PCDATA ) > <!ELEMENT version ( #PCDATA ) > <!ELEMENT customproperty ( #CDATA ) > <!ATTLIST customproperty key NMTOKEN #REQUIRED >
The elements and attributes have the following meanings:
| Element | SubElement | Description |
|---|---|---|
| SFW | The service framework XML version tag that encapsulates the service XML. Must provide the version attribute that follows the major.minor notation and must equate to supported Qt Service Framework versions. This means the minimum version is 1.0 however users are recommended to always specify the highest available version. | |
| service | The service tag can contain an arbitrary number of interface tags and one description tag. | |
| " | description | A user readable description of the purpose of the service. |
| " | filepath | The absolute path and name of the plug-in to be loaded when this service is requested. Alternatively if the plug-in name only is provided the standard library paths (see QCoreApplication::libraryPaths()) are used to find the plug-in. Note that if the plugin name is given only, platform specific parts such as the suffix ".dll" and ".so" or plugin prefix "lib" should be removed to enable cross platform resolution. QLibrary is used to determine the platform specific parts of the plugin. |
| " | ipcaddress | The socket name or path that the inter-process service will be published on that will provide clients with remote access. Should be the same name as the executable for the service without any suffix such as ".exe" etc. |
| " | name | The name of the service. |
| interface | The interface describes the properties of the interface. | |
| " | capabilities | This property is a list of arbitrary strings which are interpreted as permissions/capabilities. The list elements are comma-separated and spaces after commas are not permitted. This list can be empty. |
| " | name | The name of the interface using the Java class name notation. (e.g. com.nokia.qt.TestService) |
| " | version | This property contains the interface and implementation version. The version tag follows the major.minor notation. The major version indicates the interface version the minor version the implementation version.
The version number must be greater than 1.0. The version cannot be less than 1.0 because the Service Framework is dependent on the fact that services must be binary compatible between major versions, and services with versions less than 1.0 are unlikely to be binary compatible with later versions. |
| " | description | A user readable description of the purpose of the interface. |
| " | customproperty | An implementation specific key value pair which can be used for filtering or as description. |
An example for a valid XML service description could be the following TestService:
<?xml version="1.0" encoding="utf-8" ?> <SFW version="1.1"> <service> <name>TestService</name> <filepath>testserviceplugin</filepath> <description>Test service description</description> <interface> <name>com.nokia.qt.ILocation</name> <version>1.4</version> <capabilities></capabilities> <description>Interface that provides location support</description> </interface> <interface> <name>com.nokia.qt.ILocation</name> <version>1.5</version> <capabilities></capabilities> <description>Interface that provides location support</description> </interface> <interface> <name>com.nokia.qt.ISysInfo</name> <capabilities>ReadUserData</capabilities> <version>2.3</version> <description>Interface that provides system information support</description> <customproperty key="key1">value1</customproperty> <customproperty key="key2">value2</customproperty> </interface> </service> </SFW>
The framework includes a GUI tool under tools/servicexmlgen for generating and inspecting service XML files. This makes it easy to enter service metadata and interface details and generate the appropriate XML to describe the plugin or IPC based service. It can also be used to load and inspect existing service XML files.
Note that the tool will default to the highest known existing Qt Service Framework version as the XML version attribute and subsequent saves on loaded files will enforce this default version.
Here is a screenshot of the application, loaded with the TestService XML description provided above.
New services can be added and removed at any time via QServiceManager::addService() and QServiceManager::removeService().
On Symbian devices a service can be installed using the Symbian package installer. More details about this process can be found in the Qt Service Framework on Symbian documentation.
Each implementation is identified by a service name, an interface name and its version. This information is encapsulated by QServiceInterfaceDescriptor which can be used to request references to service objects.
QServiceFilter simplifies the lookup of already installed services. Developers specifies the criteria used during the meta data lookup. The subsequent example demonstrates the interaction between QServiceInterfaceDescriptor and QServiceFilter by creating references to all services that implement the interface com.nokia.qt.ILocation:
QServiceManager mgr; QServiceFilter filter; filter.setInterface("com.nokia.qt.ILocation"); QList<QServiceInterfaceDescriptor> list = mgr.findInterfaces(filter); for(int i = 0; i < list.size(); i++) { QObject *serviceObject; serviceObject = mgr.loadInterface(list[i]); // returned object owned by client if (serviceObject) serviceObject->setParent(this); }
There are two ways in which to upgrade a service. The first is an incremental approach whereby QServiceManager::addService() is used to register an XML descriptor whose service name already exists but defines new interface implementations. For example an already existing service, "ovi" may define version 1.0 of interface,"IDownload". QServiceManager::addService() is then called with an XML descriptor that declares itself as belonging the "ovi" service, but implements version 1.1 of the interface "IDownload". Both implementation versions will be available for use.
The second method is a replacement approach whereby an existing service is completely removed and replaced by a new service.
As an example the already existing "ovi" service may implement interface "IDownload" version 1.0, the new "ovi" service may implement "IDownload" version 1.0 and version 1.1. In this case the old service implementation must be first be removed using QServiceManager::removeService() to make way for the new service implementation.
Qt Service Framework provides a mechanism for out of process services so that clients can remotely load interfaces. These inter-process services are deployed similarly to local services, using the IPC address tag from the XML description and calling QRemoteServiceRegister::publishEntries() to add the service to the remote services manager. Clients access services via the metaobject similarly to in-process services and each remote service is represented as a QRemoteServiceRegister::Entry by using QRemoteServiceRegister::createEntry(). The Echo Client Example demonstrates how remote services can be instantiated and used.
Inter-process services are deployed using a variety of different IPC mechanisms available on the current platform and as such may inherit several limitations. For Symbian, IPC is handled by the Symbian Client-Server Framework whereas for other environments services are published using QtDBus if it is available otherwise falls back on QLocalSocket for inter-process communication.
The QtDBus module is used to provide IPC in correspondance to the Qt Service Framework architecture and provides access to signals, slots, invokable methods and properties.
The D-Bus protocol requires concept identifiers that represent D-Bus objects: service names, object paths, and interfaces. D-Bus objects are registered using a combination of the service description supplied in the service XML file. An example of this, using the previous sample XML description, is provided below.
| D-Bus Concept | Derived Name |
|---|---|
| Service Name | "com.qtmobility.sfw.TestService" |
| Object Path | "/com/nokia/qt/ILocation/1/4/" |
| Interface | "" |
When using interger types for arguments to signals and slots, bass types as defined by http://doc.trolltech.com/4.7/qdbustypesystem.html. For example, quint64 is generally equivalent to qulonglong, but all unsigned 64 bit values must be defined as qulonglong or they will not work with the dbus implementation. For more details and the current state of the limitation please refer to bug QTMOBLITY-1694 available at http://bugreports.qt.nokia.com/browse/QTMOBILITY-1694.
A current known limitation for Qt Service Framework using QtDBus for IPC is that enumerators cannot be read due to lack of support on D-Bus. This will be added in future versions once the QtDBus module enables enumerator support. A current known workaround is to manually define and use integers as demonstrated in the Declarative Serviceframework Dialer example. Furthermore, due to the nature of IPC, pointers to objects cannot be passed between services and clients. Unfortunately, this also means that anything wrapped in a typedef macro cannot be communicated effectively between processes.
D-Bus services inherit automatic start support by providing .service files to the D-Bus daemon search paths. Aside from producing these files manually, the servicefw tool provides an option to generate the corresponding files inside the local user D-Bus folder for convenience. This will allow all client requests to automatically startup the service if it isn't already running. Consequently, once every client has closed its service instance the service will be automatically terminated after invoking any slots connected to notification signals.
Running the following command will enable rendezvous for D-Bus IPC.
./servicefw dbusservice <service-xml-file> <service-file>
The .service files will typically be generated in the $home/.local/share/dbus-1/services directory unless the $$XDG_DATA_HOME environment variable is set. If the --system option is used the tool will generate the file inside /usr/share/dbus-1/services if the user permissions are met.
Note that in order for the autostart feature to function correctly, the service needs to be either pre-registered or registered at run-time so that clients can use a QServiceManager to discover the IPC interfaces that invoke the D-Bus service files. This is usually done on deployment by adding services through the servicefw tool.
Pointers to objects, and anything wrapped in a typedef cannot be passed between services and clients. It's recommended that IPC messages be kept small on Symbian when possible. Symbian Client-Server IPC mandates a fixed buffer size, currently set at 255 bytes. Messages that are large will cause a large number of context switches. This may cause a system performance pentalty if a lot of very large messages are transfered frequently.
Symbian IPC will automatically start the server process if required when the client calls loadInterface. The executable name must be the same as the name provided <ipcaddress> tag in the xml registration file. For example <ipcaddress>xyzabc</ipcaddress> should have the executable for the service called xyzabc.exe.
All services must be registered for clients to be able to locate and use them. Symbian provides 3 different methods to register services.
Automatic registration is the prefered method for services that are not Symbian Signed and don't require high levels of security. The XML file is copied into the import directory of the IPC backend. In Qt project files this can be done by:
xmlautoimport.path = /private/2002AC7F/import/ xmlautoimport.sources = <service xml file>.xml DEPLOYMENT += xmlautoimport
Or in a symbian .pkg file by:
"/epoc32/data/z/private/2002AC7F/import/<service xml file>.xml" - "c:\private\2002AC7F\import\<service xml file>.xml"
For services that are Symbian Signed and require a higher level of security they may chose to use a post install program. The authenticity check of the service is done during registration using the VID/SID. If the installer defines the VID it is stored in the registration database, and only the same VID maybe used to remove the service or reinstall it. If the VID is undefined then the SID is used. The VID/SID remain in the registration database after unregistration locking the name to the VID/SID. Only installers using the same VID/SID may register a service of the same name.
An example project can be found at examples/serviceinstaller_sfw_symbian.
More info about VID and SID can be found from
For Symbian application built into the rom image registration must be done at build time using the host tool servicedbgen. To register a service run the command:
servicedbgen -tall add <service xml file>
Appropriate iby files, and settings are required for including the service executable and related files in the rom image.
Services can install a filter function to check the credentials of a client on initial connection and then terminate connections if desired. The filter is a function:
bool securityFilter(const void *p) { const RMessage2 *aMessage = reinterpret_cast<const RMessage2*>(p); if(check_security) { return true; // accept connection } else { retun false; // reject connection } }
Returning true returns CPolicyServer::EPass and false returns CPolicyServer::EFail to the Client-Server secuity check. Registration of the filter is done by calling QRemoteServiceRegister::setSecurityFilter(). The Symbian Policy Server API can be used to work with the RMessage2 to extract security policy details, such as RMessage2::HasCapability or RMessage2::VendorId().
IPC errors can occur. QObjects returned by the service manager have an additional signal created, errorUnrecoverableIPCFault(QService::UnrecoverableIPCError) which the client must connect to. If an error occurs the object must be destroyed; no further calls can be made. The error recovery is left up to the client application.
On platforms that do not provide D-Bus or the Symbian Client-Server Framework, the underlying IPC mechanism utilized is a local socket based protocol.
Similar to the other IPC mechanisms, passing object pointers or typedefs will not work on local socket. Local socket also requires the executable for the service to be installed somewhere in your PATH for autostart to work. Not all platforms support all fields on the QRemoteServiceResgiterCredentials and will return -1 in unsupported fields.
This mechanism provides automatic service startup. The <ipcaddress> tag must be set to the executable filename. For example <ipcaddress>xyzabc</ipcaddress> must be used if the executable is xyzabc, or xyzabc.exe on windows systems. The PATH is searched for the executable. If the executable is not found, or the service does not start, then the error is reported to the client.
All services must be registered. The 'servicefw' tool registers xml files. It must be run before a service can be used. For example:
servicefw add <service xml file>
The service can install a security filter to reject connections from some clients. This applies to D-Bus and local socket implementations of IPC.
bool securityFilter(const void *p) { const QRemoteServiceRegisterCredentials *cr = (const struct QRemoteServiceRegisterCredentials *)p; if(cr->uid == 0) { return true; // accept connection } else { retun false; // reject connection } } struct QRemoteServiceRegisterCredentials { int fd; int pid; int uid; int gid; };
Returning true accepts the connect, false terminates it. Certain platforms do not provide all the results, and undefined values are set to -1. Registration of the filter is done by calling QRemoteServiceRegister::setSecurityFilter(). Only 1 filter maybe installed at one time.
Out of process services behave similarly to local services, with one exception. There can be IPC errors, or the remote service can terminate unexpectedly. QObjects returned by the service manager for out of process services have an additional signal created, errorUnrecoverableIPCFault(QService::UnrecoverableIPCError) which the client must connect to. If an error occurs the object must be destroyed; no further calls can be made. The error recovery is left up to the client application.
|
Represents a remote service entry to be published on QRemoteServiceRegister |
|
|
Generic mechanism to enable permission checks for services |
|
|
Manages instances of remote service objects |
|
|
Contains miscellaneous identifiers used throughout the Qt Service framework library |
|
|
Context information to services |
|
|
Defines criteria for defining a sub-set of all available services |
|
|
Identifies a service implementation |
|
|
Enables the loading of service plugins and the (de)registration of services |
|
|
Defines the interface that every plug-in based service must implement |
The Qt Service Framework offers discovery and selection of services through declarative UI by providing service and service list elements. Detailed information can be found at QML Service Framework Plugin.
|
The Service element holds an instance of a service object. |
|
|
The ServiceList element holds a list of Service elements. |