AddMatchWithID / RemoveMatchById

Havoc Pennington hp at
Tue Feb 19 17:21:35 PST 2008


Can you elaborate on the client library API this is intended to
support? In particular it isn't clear to me when I would want to know
that a signal comes from a match rule, vs. simply what the signal is.
It seems to me that if I do xyz when FooHappened, the match rule that
caused me to know that FooHappened should not be relevant.

One quick note, I think one library will always own a given socket
connected to dbus-daemon; whatever that library is can keep track of
IDs in use. So adding a round trip to get the ID doesn't seem
necessary, it's fine if the client lib tracks what's in use. Any code
module in the app can ask the client lib what ID to use, or am I
missing something?


More information about the dbus mailing list