[maemo-developers] D-BUS service name confusion

From: Eero Tamminen eero.tamminen at nokia.com
Date: Wed May 28 14:34:25 EEST 2008
Hi,

ext Axel Sommerfeldt wrote:
> In the Maemo 4.0 Tutorial, section "Integrating Applications to maemo 
> Framework", there is an example desktop file with the line:
> 
> X-Osso-Service=org.maemo.example_libosso
> 
> But when I take a look at the examples provided by Nokia, only the 
> application name is stated here, for example:
> 
> X-Osso-Service=maemopad
> 
> But which one is correct, the "long" term (found in the Tutorial) or the 
> "short" term (found in the maemopad example)?
> 
> Which confuses me even more is a statement found in the documentation of 
> osso_initialize(): [1]
> 
> "Note that the D-BUS service name will be 'com.nokia.application', where 
> 'application' is the value you gave as the parameter."
> 
> So a DBUS service name have to be "com.nokia.<your-application-name-here>"?
> 
> Furthermore one can found there:
> 
> "Note also that this argument must be identical to the X-Osso-Service 
> value in the desktop file, or the D-BUS daemon will kill your application."
> 
> Mixing all of this together, I come to the conclusion that the "short" 
> X-Osso-Service line is correct (because the argument of 
> osso_initialize() must be identical to this value) and using a DBUS 
> service name like "org.maemo.example_libosso" is wrong, because it must 
> be "com.nokia.example_libosso" instead. Is this correct?
> 
> At least the Tutorial is inconsistent to the example and to the 
> documentation of osso_initialize(). But what information is correct and 
> what is wrong?
> 
> [1] http://maemo.org/api_refs/4.0/libosso/index.html

Please file a bug against documentation to bugs.maemo.org
with the above details.

AFAIK com.nokia. is automatically prepended to service names
that contain only one path element (no dots).  I think it
would be better to use a long name as "com.nokia." is not
appropriate service prefix for 3rd party software.


	- Eero

More information about the maemo-developers mailing list