Signal filtering

[Philip Van Hoof]

On Mon, 2005-08-29 at 15:02 -0400, John (J5) Palmieri wrote:

> There isn't much documentation.  Like I said it is on the TODO list.
> But lets take NameOwnerChanged for instance.  You can only match on
> strings with arg matches which makes this signal perfect.  Say you want
> to receive signals from only org.freedesktop.Foo you would do this:
> 
> dbus_bus_add_match (dbus_connection,
>                     "type='signal',"
>                     "interface='org.freedesktop.DBus',"
>                     "memeber='NameOwnerChanged',"
>                     "arg0='org.freedesktop.Foo'", &error);

Is arg0 "any string"? Could it be like this?

"arg0='/some/tests/testing1'" or
"arg0='/some/tests/testing2'" or
"arg0='/some/tests/testing3'" or
"arg0='/some/tests/more/testing4'" or


And can I let the filter succeed on tests like this?

"arg0='/some/tests/*'"

So an argument for testing1, testing2, testing3 and even more/testing4.

The purpose is, indeed, a specification for a system like gconf. Not yet
a software or implemented infrastructure. A.t.m. it's just for defining
a specification. Don't worry :p.


-- 
Philip Van Hoof, software developer at x-tend
home: me at pvanhoof dot be
gnome: pvanhoof at gnome dot org
work: vanhoof at x-tend dot be
http://www.pvanhoof.be - http://www.x-tend.be