2 - Message matching rules (so broadcasts can be filtered) need sorting
5 - How we will handle DCOP needs sorting out. Among other things, we
6 need to check that service and service-ownership semantics map to DCOP
9 - Activation needs some careful additional thinking-through.
11 - Property list feature on message bus (list of properties associated
12 with a connection). May also include message matching rules
13 that involve the properties of the source or destination
16 - Implement all the needed resource limits to keep clients from
17 killing the message bus.
19 - Automatic service activation, should probably be done through a message flag.
21 - Disconnecting the remote end on invalid UTF-8 is probably not a good
22 idea. The definitiion of "valid" is slightly fuzzy. I think it might
23 be better to just silently "fix" the UTF-8, or perhaps return an error.
25 Owen says we should only validate the UTF-8 on dbus_message_get_string()
26 (changing get_string to have an error return, and allowing a type error
29 - We might consider returning a "no such operation" error in dbus-connection.c
30 for unhandled messages.
32 - The convenience functions in dbus-bus.h should perhaps have
33 the signatures that they would have if they were autogenerated
34 stubs. e.g. the acquire service function. We should also evaluate
35 which of these functions to include, in light of the fact that
36 GLib/Qt native stubs will probably also exist.
38 - The message handler interface needs rethinking, perhaps handlers should be able
39 to return an error that automatically gets turned into a message; most likely
40 some basic spec'ing out of the GLib/Qt level stubs/skels stuff will be
41 needed to understand the right approach.
43 - there are various bits of code to manage ref/unref of data slots, that should
44 be merged into a generic facility
46 - assorted _-prefixed symbols in libdbus aren't actually used by
47 libdbus, only by the message bus. These bloat up the library
48 size. Not sure how to fix, really.
50 - if you send a message to a service then block for reply, and the service exits/crashes
51 after the message bus has processed your message but before the service has replied,
52 it would be nice if the message bus sent you an error reply.