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 - publish the introspection dtd at its URL
26 - RequestName flags seem a bit strange; see the docs for dbus_bus_request_name()
27 and think about use cases in better detail.
29 http://lists.freedesktop.org/archives/dbus/2005-August/003207.html
31 Kind of a major API change, but seems high-value.
33 - figure out what the deal is with trailing nul bytes in
35 http://lists.freedesktop.org/archives/dbus/2005-August/003179.html
38 Important for 1.0 GLib Bindings
41 - Test point-to-point mode
43 - Add support for getting sender
45 - format_version in the object info doesn't look like it's handled correctly. The creator
46 of the object info should specify some fixed number per struct version; the library
47 should handle only specific numbers it knows about. There's no assumption that all
48 numbers >= the given one are compatible. The idea is that new versions of the lib
49 can offer totally different object info structs, but old versions
52 Important for 1.0 Python bindings
57 - Fix removing of signals from the match tree
59 - Fix refcounting and userdata lifecycles
61 - Write a generic mainloop
66 - protocol version in each message is pretty silly
71 - if the GUID is obtained only during authentication, not in the address,
72 we could still share the connection
74 - Allow a dbus_g_proxy_to_string()/g_object_to_string() that
75 would convert the proxy to an "IOR" and dbus_g_proxy_from_string()
76 that would decode; using these, dbus-glib users could avoid
77 DBusConnection entirely. Of course the same applies to other kinds
78 of binding. This would use dbus_connection_open()'s connection-sharing
79 feature to avoid massive proliferation of connections.
81 - DBusWatchList/TimeoutList duplicate a lot of code, as do
82 protected_change_watch/protected_change_timeout in dbus-connection.c
83 and dbus-server.c. This could all be mopped up, cut-and-paste
84 fixed, code size reduced.
86 - change .service files to allow Names=list in addition to Name=string
88 - The message bus internal code still says "service" for
89 "name", "base service" for "unique name", "activate" for
90 "start"; would be nice to clean up.
92 - Property list feature on message bus (list of properties associated
93 with a connection). May also include message matching rules
94 that involve the properties of the source or destination
97 - Disconnecting the remote end on invalid UTF-8 is probably not a good
98 idea. The definition of "valid" is slightly fuzzy. I think it might
99 be better to just silently "fix" the UTF-8, or perhaps return an error.
101 - build and install the Doxygen manual in Makefile when --enable-docs
103 - if you send the same message to multiple connections, the serial number
104 will only be right for one of them. Probably need to just write() the serial
105 number, rather than putting it in the DBusMessage, or something.
107 - perhaps the bus driver should have properties that reflect attributes
108 of the session, such as hostname, architecture, operating system,
109 etc. Could be useful for code that wants to special-case behavior
110 for a particular host or class of hosts, for example.
112 - currently the security policy stuff for messages to/from
113 the bus driver is kind of strange; basically it's hardcoded that
114 you can always talk to the driver, but the default config file
115 has rules for it anyway, or something. it's conceptually
116 screwy at the moment.
118 - when making a method call, if the call serial were globally unique,
119 we could forward the call serial along with any method calls made
120 as a result of the first method call, and allow reentrancy that was
121 strictly part of the call stack of said method call. But I don't
122 really see how to do this without making the user pass around the
123 call serial to all method calls all the time, or disallowing
126 If done post 1.0 will probably be an optional/ugly-API type
129 - I don't want to introduce DBusObject, but refcounting and object
130 data could still be factored out into an internal "base class"
133 - Keep convenience wrappers in sync with bus methods
135 - document the auth protocol as a set of states and transitions, and
136 then reimplement it in those terms
138 - recursive dispatch, see dbus_connection_dispatch()
140 - do we need per-display activation; if so I'd like to do this by setting a
141 "display ID" property on screen 0, with a GUID, and keying activation by
142 said GUID. Otherwise you get all kinds of unrobust
143 string/hostname-based mess. per-screen is then done by appending screen number
144 to the display. If displays have a deterministic ID like this, you can
145 do per-display by simply including GUID in the service name.
147 - optimization and profiling!
149 - Match rules aren't in the spec (probably a lot of methods on the bus
155 - look into supporting the concept of a "connection" generically