4 - Remove all deprecated functions
6 - Audit @todo and FIXME for security issues
8 - the "break loader" and valid/invalid message tests are all disabled;
9 they need to be fixed and re-enabled with the new message args stuff.
10 I think I want to drop the .message files thing and just have code
11 that generates messages, more like the tests for
12 dbus-marshal-recursive.c (this is mostly done now, just needs some
15 - need to define bus behavior if you send a message to
16 yourself; is it an error, or allowed? If allowed,
17 we need to have a test for it in the test suite.
19 - just before 1.0, try a HAVE_INT64=0 build and be sure it runs
21 - dbus-pending-call.c has some API and thread safety issues to review
23 - Add test harness for selinux allow/deny cf. this message
24 http://lists.freedesktop.org/archives/dbus/2005-April/002506.html
26 - Add a test case for handling the Ping message
28 Important for 1.0 GLib Bindings
31 - Annotations for "do not take ownership of this return value" on server
35 - Test point-to-point mode
37 - Add support for getting sender
42 - protocol version in each message is pretty silly
47 - if the GUID is obtained only during authentication, not in the address,
48 we could still share the connection
50 - Allow a dbus_g_proxy_to_string()/g_object_to_string() that
51 would convert the proxy to an "IOR" and dbus_g_proxy_from_string()
52 that would decode; using these, dbus-glib users could avoid
53 DBusConnection entirely. Of course the same applies to other kinds
54 of binding. This would use dbus_connection_open()'s connection-sharing
55 feature to avoid massive proliferation of connections.
57 - DBusWatchList/TimeoutList duplicate a lot of code, as do
58 protected_change_watch/protected_change_timeout in dbus-connection.c
59 and dbus-server.c. This could all be mopped up, cut-and-paste
60 fixed, code size reduced.
62 - change .service files to allow Names=list in addition to Name=string
64 - The message bus internal code still says "service" for
65 "name", "base service" for "unique name", "activate" for
66 "start"; would be nice to clean up.
68 - Property list feature on message bus (list of properties associated
69 with a connection). May also include message matching rules
70 that involve the properties of the source or destination
73 - Disconnecting the remote end on invalid UTF-8 is probably not a good
74 idea. The definition of "valid" is slightly fuzzy. I think it might
75 be better to just silently "fix" the UTF-8, or perhaps return an error.
77 - build and install the Doxygen manual in Makefile when --enable-docs
79 - if you send the same message to multiple connections, the serial number
80 will only be right for one of them. Probably need to just write() the serial
81 number, rather than putting it in the DBusMessage, or something.
83 - perhaps the bus driver should have properties that reflect attributes
84 of the session, such as hostname, architecture, operating system,
85 etc. Could be useful for code that wants to special-case behavior
86 for a particular host or class of hosts, for example.
88 - currently the security policy stuff for messages to/from
89 the bus driver is kind of strange; basically it's hardcoded that
90 you can always talk to the driver, but the default config file
91 has rules for it anyway, or something. it's conceptually
94 - when making a method call, if the call serial were globally unique,
95 we could forward the call serial along with any method calls made
96 as a result of the first method call, and allow reentrancy that was
97 strictly part of the call stack of said method call. But I don't
98 really see how to do this without making the user pass around the
99 call serial to all method calls all the time, or disallowing
102 If done post 1.0 will probably be an optional/ugly-API type
105 - I don't want to introduce DBusObject, but refcounting and object
106 data could still be factored out into an internal "base class"
109 - document the auth protocol as a set of states and transitions, and
110 then reimplement it in those terms
112 - recursive dispatch, see dbus_connection_dispatch()
114 - do we need per-display activation; if so I'd like to do this by setting a
115 "display ID" property on screen 0, with a GUID, and keying activation by
116 said GUID. Otherwise you get all kinds of unrobust
117 string/hostname-based mess. per-screen is then done by appending screen number
118 to the display. If displays have a deterministic ID like this, you can
119 do per-display by simply including GUID in the service name.
121 - optimization and profiling!
126 - look into supporting the concept of a "connection" generically