Service names and object paths

[Havoc Pennington]

Hi,

On Mon, Dec 27, 2010 at 8:21 AM, Alberto Mardegan
<mardy at users.sourceforge.net> wrote:
> I see... Then this means that object paths exist only on the process which
> registered them, and that the D-Bus server is not aware of them, right?
>

Exactly. Object path routes messages *within* the connected process
(selects an object inside the app), while bus name routes messages
*among* processes on the bus (selects which apps get the message).

One reason for this is to allow apps to have lots of objects (even 1
per spreadsheet cell or something). If you had to register with the
bus then you'd have some per-object data structure overhead and
registration IPC overhead. With the dbus model, objects can be lazily
created or "virtual" (for example, all spreadsheet cell paths might be
routed to the same implementation object).

Havoc