AddMatchWithID / RemoveMatchById
simon.mcvittie at collabora.co.uk
Wed Feb 20 02:18:35 PST 2008
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 19 Feb 2008 at 20:21:35 -0500, Havoc Pennington wrote:
> One quick note, I think one library will always own a given socket
> connected to dbus-daemon
The main reason I'm still considering having dbus-python remain a
libdbus binding rather than a full implementation (and similar for the
GLib bindings, potentially) is the bus DBusConnection sharing, so this
statement makes me somewhat puzzled!
Or are you saying that libdbus will be the "socket owner" for these purposes,
even if it's things like dbus-glib and dbus-python that actually want to use
This API would somewhat work against bindings that wanted to merge similar
match rules to avoid the bus daemon's match-rule limit (something I've
considered for dbus-python - always matching as specifically as possible, then
doing some sort of automatic merging if we're adding too many rules), although
the match-rule limit has been relaxed in recent versions anyway.
How are client implementations expected to discover whether the bus
daemon supports this new functionality? Try it, do the round trip, and
fall back to the old way if not?
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
More information about the dbus