4 - Audit @todo and FIXME for security issues
6 - The convenience functions in dbus-bus.h should perhaps have
7 the signatures that they would have if they were autogenerated
8 stubs. e.g. the acquire service function. We should also evaluate
9 which of these functions to include, in light of the fact that
10 GLib/Qt native stubs will probably also exist.
12 - the "break loader" and valid/invalid message tests are all disabled;
13 they need to be fixed and re-enabled with the new message args stuff.
14 I think I want to drop the .message files thing and just have code
15 that generates messages, more like the tests for
16 dbus-marshal-recursive.c (this is mostly done now, just needs some
19 - need to define bus behavior if you send a message to
20 yourself; is it an error, or allowed? If allowed,
21 we need to have a test for it in the test suite.
23 - validate dict entry number of fields
25 - just before 1.0, try a HAVE_INT64=0 build and be sure it runs
27 - in dbus-keyring.c, enforce that the keyring dir is not
28 world readable/writable
32 - fix introspection format to handle all signatures
34 - make the mutex/condvar functions private
36 - dbus-pending-call.c has some API and thread safety issues to review
38 Important for 1.0 GLib Bindings
41 - finish dbus-glib-tool support for adding introspection
42 data to GObject and autoexporting GObject using same
44 - Need to make sure that dbus-glib.h never returns any
45 dbus_malloc() memory, only g_malloc().
46 dbus_g_proxy_end_call() is the major offender.
48 - DBusGProxy doesn't emit "destroy" when it should
53 - add dbus_message_has_path(), maybe has_member/interface
55 - connection_open/connection_disconnect lacks symmetry, open/close
58 - protocol version in each message is pretty silly
63 - change .service files to allow Names=list in addition to Name=string
65 - The message bus internal code still says "service" for
66 "name", "base service" for "unique name", "activate" for
67 "start"; would be nice to clean up.
69 - Property list feature on message bus (list of properties associated
70 with a connection). May also include message matching rules
71 that involve the properties of the source or destination
74 - Disconnecting the remote end on invalid UTF-8 is probably not a good
75 idea. The definition of "valid" is slightly fuzzy. I think it might
76 be better to just silently "fix" the UTF-8, or perhaps return an error.
78 - build and install the Doxygen manual in Makefile when --enable-docs
80 - if you send the same message to multiple connections, the serial number
81 will only be right for one of them. Probably need to just write() the serial
82 number, rather than putting it in the DBusMessage, or something.
84 - perhaps the bus driver should have properties that reflect attributes
85 of the session, such as hostname, architecture, operating system,
86 etc. Could be useful for code that wants to special-case behavior
87 for a particular host or class of hosts, for example.
89 - currently the security policy stuff for messages to/from
90 the bus driver is kind of strange; basically it's hardcoded that
91 you can always talk to the driver, but the default config file
92 has rules for it anyway, or something. it's conceptually
95 - when making a method call, if the call serial were globally unique,
96 we could forward the call serial along with any method calls made
97 as a result of the first method call, and allow reentrancy that was
98 strictly part of the call stack of said method call. But I don't
99 really see how to do this without making the user pass around the
100 call serial to all method calls all the time, or disallowing
103 If done post 1.0 will probably be an optional/ugly-API type
106 - I don't want to introduce DBusObject, but refcounting and object
107 data could still be factored out into an internal "base class"
110 - document the auth protocol as a set of states and transitions, and
111 then reimplement it in those terms
113 - recursive dispatch, see dbus_connection_dispatch()
115 - do we need per-display activation; if so I'd like to do this by setting a
116 "display ID" property on screen 0, with a GUID, and keying activation by
117 said GUID. Otherwise you get all kinds of unrobust
118 string/hostname-based mess. per-screen is then done by appending screen number
119 to the display. If displays have a deterministic ID like this, you can
120 do per-display by simply including GUID in the service name.
122 - optimization and profiling!