DBus 1.1.4 and weird message handling

John (J5) Palmieri johnp at redhat.com
Fri Jan 25 14:08:00 PST 2008


On Thu, 2008-01-24 at 16:56 +0100, Thiago Macieira wrote:
> On Thursday 24 January 2008 16:36:55 Ross Burton wrote:
> > Aside from the point that notify messages should be signals, this means
> > that every gconf-using application was getting the messages intended for
> > the server.  I've fixed this by adding "member='Notify'" and that
> > appears to work, but as to how this worked on DBus 1.0 is a very good
> > question...
> >
> > Did messages sent to named services only get sent there, instead of
> > everyone who was listening?  I'm also wondering if the bus sniffing
> > fixes have led to more clients getting messages.
> 
> Eavesdropping was probably disabled in 1.0 but is allowed in 1.1. That's how 
> you're getting messages that you're not usually entitled to.
> 

More to the point, Eavesdropping was broken in 1.0 for certain kinds of
messages.  It was always turned on on the session bus.

-- 
John (J5) Palmieri <johnp at redhat.com>



More information about the dbus mailing list