2 - Service and message names should be more carefully restricted;
3 they should have a max length, may not be an empty string,
4 and perhaps should not be allowed to be a glob such as "*" since
5 the config file could conveniently use such notation.
7 Suggest requiring length > 0, length < max,
8 name contains at least one ".", no initial ".", and valid UTF-8.
9 That would prohibit plain "*" but not "foo.bar.baz.operator*"
11 For maximum convenience from all programming languages, we could go
12 further and just categorically ban nearly all non-alphanumeric
15 - Message matching rules (so broadcasts can be filtered) need sorting
18 - How we will handle DCOP needs sorting out. Among other things, we
19 need to check that service and service-ownership semantics map to DCOP
22 - Activation needs some careful additional thinking-through.
24 - Recursive/composite/etc. types and associated API, see mailing list.
26 - dbus-bus.h should contain convenience API for connecting to system
27 and login-session message buses (automatically handling env
30 - Configuration file (working on that now)
32 - Property list feature on message bus (list of properties associated
33 with a connection). May also include message matching rules
34 that involve the properties of the source or destination
37 - Implement all the needed resource limits to keep clients from
38 killing the message bus.