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 - just before 1.0, try a HAVE_INT64=0 build and be sure it runs
17 - dbus-pending-call.c has some API and thread safety issues to review
19 - Add test harness for selinux allow/deny cf. this message
20 http://lists.freedesktop.org/archives/dbus/2005-April/002506.html
22 - Add a test case for handling the Ping message
24 - Add match on args or match on details to match rules
26 Important for 1.0 GLib Bindings
29 - Test point-to-point mode
31 - Add support for getting sender
33 Important for 1.0 Python bindings
38 - Fix removing of signals from the match tree
40 - Fix refcounting and userdata lifecycles
42 - Write a generic mainloop
47 - protocol version in each message is pretty silly
52 - if the GUID is obtained only during authentication, not in the address,
53 we could still share the connection
55 - Allow a dbus_g_proxy_to_string()/g_object_to_string() that
56 would convert the proxy to an "IOR" and dbus_g_proxy_from_string()
57 that would decode; using these, dbus-glib users could avoid
58 DBusConnection entirely. Of course the same applies to other kinds
59 of binding. This would use dbus_connection_open()'s connection-sharing
60 feature to avoid massive proliferation of connections.
62 - DBusWatchList/TimeoutList duplicate a lot of code, as do
63 protected_change_watch/protected_change_timeout in dbus-connection.c
64 and dbus-server.c. This could all be mopped up, cut-and-paste
65 fixed, code size reduced.
67 - change .service files to allow Names=list in addition to Name=string
69 - The message bus internal code still says "service" for
70 "name", "base service" for "unique name", "activate" for
71 "start"; would be nice to clean up.
73 - Property list feature on message bus (list of properties associated
74 with a connection). May also include message matching rules
75 that involve the properties of the source or destination
78 - Disconnecting the remote end on invalid UTF-8 is probably not a good
79 idea. The definition of "valid" is slightly fuzzy. I think it might
80 be better to just silently "fix" the UTF-8, or perhaps return an error.
82 - build and install the Doxygen manual in Makefile when --enable-docs
84 - if you send the same message to multiple connections, the serial number
85 will only be right for one of them. Probably need to just write() the serial
86 number, rather than putting it in the DBusMessage, or something.
88 - perhaps the bus driver should have properties that reflect attributes
89 of the session, such as hostname, architecture, operating system,
90 etc. Could be useful for code that wants to special-case behavior
91 for a particular host or class of hosts, for example.
93 - currently the security policy stuff for messages to/from
94 the bus driver is kind of strange; basically it's hardcoded that
95 you can always talk to the driver, but the default config file
96 has rules for it anyway, or something. it's conceptually
99 - when making a method call, if the call serial were globally unique,
100 we could forward the call serial along with any method calls made
101 as a result of the first method call, and allow reentrancy that was
102 strictly part of the call stack of said method call. But I don't
103 really see how to do this without making the user pass around the
104 call serial to all method calls all the time, or disallowing
107 If done post 1.0 will probably be an optional/ugly-API type
110 - I don't want to introduce DBusObject, but refcounting and object
111 data could still be factored out into an internal "base class"
114 - Keep convenience wrappers in sync with bus methods
116 - document the auth protocol as a set of states and transitions, and
117 then reimplement it in those terms
119 - recursive dispatch, see dbus_connection_dispatch()
121 - do we need per-display activation; if so I'd like to do this by setting a
122 "display ID" property on screen 0, with a GUID, and keying activation by
123 said GUID. Otherwise you get all kinds of unrobust
124 string/hostname-based mess. per-screen is then done by appending screen number
125 to the display. If displays have a deterministic ID like this, you can
126 do per-display by simply including GUID in the service name.
128 - optimization and profiling!
133 - look into supporting the concept of a "connection" generically