Hi Richi,
You do know that the object path is specific to the daemon that provides
it anyway. The access to a method or signal of an interface is done via
the unique bus name _and_ the object path.
This means that daemon A can register /org/foo and daemon B can
register /org/foo and
Marcel Holtmann wrote:
[...]
Okay so there has been a fair amount of discussion here but I think
we've veered off track a bit. To try to re-phrase my thoughts:
- Current DBus object paths are application-centric (this is by
choice of the application)
- Without a well-known set of paths
Hi Jim,
Okay so there has been a fair amount of discussion here but I think
we've veered off track a bit. To try to re-phrase my thoughts:
- Current DBus object paths are application-centric (this is by
choice of the application)
the object paths are specific to the daemon (I prefer
ti, 2007-01-30 kello 10:58 +, Jim McDonald kirjoitti:
- Current DBus object paths are application-centric (this is by
choice of the application)
[..snip..]
- There seem to be two options (ignoring the uninteresting ones):
- take a combination of the existing
Marcel Holtmann wrote:
[...]
the question is still why. We have EDS. So no reason to invent another
interface for the same purpose. Don't try to over-complicate things.
So this is an argument against abstraction, which I understand but
disagree with. It comes back to the two choices that
Hi marcel,
the question is still why. We have EDS. So no reason to invent another
interface for the same purpose. Don't try to over-complicate things.
I'm not saying that there should be any change to dbus as it is. I'm
only advocating the 'well-known' part of this all.
I'm saying that it's
Hi Kalle,
the question is still why. We have EDS. So no reason to invent another
interface for the same purpose. Don't try to over-complicate things.
I'm not saying that there should be any change to dbus as it is. I'm
only advocating the 'well-known' part of this all.
nobody was talking
On Tuesday 30 January 2007 05:03, Marcel Holtmann scribbled in crayon on the
back of a kid's menu:
And again. Nobody is going to change D-Bus. It works like it does, but
you need to understand how it works.
Newbie to Dbus question: any suggestions for a good place to get started on
gaining
Therefore it'd require a lot of standardisation to create such a thing
where these all would be just another device of type X. If this was
possible then we *could* have a dbus address that has a program that
could advertise these features. Like this:
/xx/yy/zz NETWORKING_FEATURE
9 matches
Mail list logo
