4 - Remove all deprecated functions
6 - Audit @todo and FIXME for security issues
8 - The convenience functions in dbus-bus.h should perhaps have
9 the signatures that they would have if they were autogenerated
10 stubs. e.g. the acquire service function. We should also evaluate
11 which of these functions to include, in light of the fact that
12 GLib/Qt native stubs will probably also exist.
14 - the "break loader" and valid/invalid message tests are all disabled;
15 they need to be fixed and re-enabled with the new message args stuff.
16 I think I want to drop the .message files thing and just have code
17 that generates messages, more like the tests for
18 dbus-marshal-recursive.c (this is mostly done now, just needs some
21 - need to define bus behavior if you send a message to
22 yourself; is it an error, or allowed? If allowed,
23 we need to have a test for it in the test suite.
25 - validate dict entry number of fields
27 - just before 1.0, try a HAVE_INT64=0 build and be sure it runs
29 - in dbus-keyring.c, enforce that the keyring dir is not
30 world readable/writable
34 - dbus-pending-call.c has some API and thread safety issues to review
36 - Add test harness for selinux allow/deny cf. this message
37 http://lists.freedesktop.org/archives/dbus/2005-April/002506.html
39 Important for 1.0 GLib Bindings
42 - finish dbus-glib-tool support for adding introspection
43 data to GObject and autoexporting GObject using same
45 - Need to make sure that dbus-glib.h never returns any
46 dbus_malloc() memory, only g_malloc().
47 dbus_g_proxy_end_call() is the major offender.
49 - DBusGProxy doesn't emit "destroy" when it should
54 - add dbus_message_has_path(), maybe has_member/interface
56 - protocol version in each message is pretty silly
61 - if the GUID is obtained only during authentication, not in the address,
62 we could still share the connection
64 - Allow a dbus_g_proxy_to_string()/g_object_to_string() that
65 would convert the proxy to an "IOR" and dbus_g_proxy_from_string()
66 that would decode; using these, dbus-glib users could avoid
67 DBusConnection entirely. Of course the same applies to other kinds
68 of binding. This would use dbus_connection_open()'s connection-sharing
69 feature to avoid massive proliferation of connections.
71 - DBusWatchList/TimeoutList duplicate a lot of code, as do
72 protected_change_watch/protected_change_timeout in dbus-connection.c
73 and dbus-server.c. This could all be mopped up, cut-and-paste
74 fixed, code size reduced.
76 - change .service files to allow Names=list in addition to Name=string
78 - The message bus internal code still says "service" for
79 "name", "base service" for "unique name", "activate" for
80 "start"; would be nice to clean up.
82 - Property list feature on message bus (list of properties associated
83 with a connection). May also include message matching rules
84 that involve the properties of the source or destination
87 - Disconnecting the remote end on invalid UTF-8 is probably not a good
88 idea. The definition of "valid" is slightly fuzzy. I think it might
89 be better to just silently "fix" the UTF-8, or perhaps return an error.
91 - build and install the Doxygen manual in Makefile when --enable-docs
93 - if you send the same message to multiple connections, the serial number
94 will only be right for one of them. Probably need to just write() the serial
95 number, rather than putting it in the DBusMessage, or something.
97 - perhaps the bus driver should have properties that reflect attributes
98 of the session, such as hostname, architecture, operating system,
99 etc. Could be useful for code that wants to special-case behavior
100 for a particular host or class of hosts, for example.
102 - currently the security policy stuff for messages to/from
103 the bus driver is kind of strange; basically it's hardcoded that
104 you can always talk to the driver, but the default config file
105 has rules for it anyway, or something. it's conceptually
106 screwy at the moment.
108 - when making a method call, if the call serial were globally unique,
109 we could forward the call serial along with any method calls made
110 as a result of the first method call, and allow reentrancy that was
111 strictly part of the call stack of said method call. But I don't
112 really see how to do this without making the user pass around the
113 call serial to all method calls all the time, or disallowing
116 If done post 1.0 will probably be an optional/ugly-API type
119 - I don't want to introduce DBusObject, but refcounting and object
120 data could still be factored out into an internal "base class"
123 - document the auth protocol as a set of states and transitions, and
124 then reimplement it in those terms
126 - recursive dispatch, see dbus_connection_dispatch()
128 - do we need per-display activation; if so I'd like to do this by setting a
129 "display ID" property on screen 0, with a GUID, and keying activation by
130 said GUID. Otherwise you get all kinds of unrobust
131 string/hostname-based mess. per-screen is then done by appending screen number
132 to the display. If displays have a deterministic ID like this, you can
133 do per-display by simply including GUID in the service name.
135 - optimization and profiling!