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 - Automatic service activation, should probably be done through a message flag.
18 - Disconnecting the remote end on invalid UTF-8 is probably not a good
19 idea. The definitiion of "valid" is slightly fuzzy. I think it might
20 be better to just silently "fix" the UTF-8, or perhaps return an error.
22 Owen says we should only validate the UTF-8 on dbus_message_get_string()
23 (changing get_string to have an error return, and allowing a type error
26 - We might consider returning a "no such operation" error in dbus-connection.c
27 for unhandled messages.
29 - The convenience functions in dbus-bus.h should perhaps have
30 the signatures that they would have if they were autogenerated
31 stubs. e.g. the acquire service function. We should also evaluate
32 which of these functions to include, in light of the fact that
33 GLib/Qt native stubs will probably also exist.
35 - The message handler interface needs rethinking, perhaps handlers should be able
36 to return an error that automatically gets turned into a message; most likely
37 some basic spec'ing out of the GLib/Qt level stubs/skels stuff will be
38 needed to understand the right approach.
40 - there are various bits of code to manage ref/unref of data slots, that should
41 be merged into a generic facility
43 - assorted _-prefixed symbols in libdbus aren't actually used by
44 libdbus, only by the message bus. These bloat up the library
45 size. Not sure how to fix, really.
47 - if you send a message to a service then block for reply, and the service exits/crashes
48 after the message bus has processed your message but before the service has replied,
49 it would be nice if the message bus sent you an error reply.
51 - write a DTD for the dbus-daemon-1 configuration file
53 - build and install the Doxygen manual in Makefile when --enable-docs
55 - if you send the same message to multiple connections, the serial number
56 will only be right for one of them. Probably need to just write() the serial
57 number, rather than putting it in the DBusMessage, or something.
59 - currently the security policy stuff for messages to/from
60 the bus driver is kind of strange; basically it's hardcoded that
61 you can always talk to the driver, but the default config file
62 has rules for it anyway, or something. it's conceptually