[LAD] LADI

[Bob Ham]

On Wed, 2009-12-23 at 13:28 +0200, Nedko Arnaudov wrote:
> Bob Ham <rah at bash.sh> writes:
> 
> > On Tue, 2009-12-22 at 23:21 +0200, Nedko Arnaudov wrote:

> >> D-Bus *can* span over multiple hosts.
> >
> > The main issue isn't whether D-Bus clients can connect to buses on a
> > different host.  The main issue is whether D-Bus clients connected to
> > one bus can send messages to objects on a different bus.
> 
> Applications can connect to multiple buses. Even applications that don't
> interract with remote machines do it. There are two standard local
> buses, the session bus and the system bus. Here is a screenshot of a
> dbus application called d-feet that shows two buses connected:

That application will necessarily have two connection objects within it
(eg, DBusGConnection,) encapsulating connections to the two buses.  If
you could have just one client object and use it to send messages to
objects on both buses, that would be great.  Unfortunately, that isn't
what D-Bus does.


> > I was actually labouring under the impression that D-Bus as-is could
> > cope with connecting to remote hosts because it uses sockets.  That this
> > isn't the case is, in fact *another* problem with D-Bus.
> >
> > D-Bus clients can't send messages to objects on remote buses.  As-is,
> > they can't even connect to buses on remote hosts.  Shocking.
> 
> I already replied to this:

My comment was less a criticism of your approach to LADISH development
and more a general criticism of using D-Bus for a network-wide audio
session system.

-- 
Bob Ham <rah at bash.sh>