More about "intents": Several improvements to desktop files and caches

Kevin Krammer krammer at
Mon Jan 6 12:13:12 PST 2014


On Monday, 2014-01-06, 13:24:28, Ryan Lortie wrote:
> hi,
> On Mon, Jan 6, 2014, at 10:31, Kevin Krammer wrote:
> > Wouldn't it make more sense to be able to derive the object path from the
> > name?
> > This way an application which has multiple interfaces can implement them
> > with
> > different objects but could opt to just register the same object for
> > multiple
> > paths.
> > 
> > Having a fixed path makes the second case easier but the first hard or
> > impossible.
> This isn't really how D-Bus works.  You can register multiple interfaces
> at the same object path independently of each other.

I know, sorry for the misunderstanding, let me try to rephrase:

at least in the object oriented languages which have D-Bus bindings, it is 
common to have a single object instance per D-Bus object path.
Such an object can, of course, implement multiple interfaces.

If the intents specification declares that there is only a single object path 
for intents interfaces, then this is limiting the developer to exactly that 
choice (or using a mediator object the demultiplexes, i.e. a lot more work).

If the specification has one path per interface, then developers can easily 
still have one object for all paths/interfaces, but also one object per 

Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the xdg mailing list