4 - add a new return code from dbus_connection_dispatch() called
5 IN_PROGRESS or RECURSED or something, indicating that DATA_REMAINS
6 but another dispatch is in progress, so we can't dispatch at
7 this time. OR maybe just switch to recursive locks for the dispatch
8 locks. Fixes the recursive deadlock. See the @todo for more
9 and this thread: http://lists.freedesktop.org/archives/dbus/2006-February/004128.html
11 - Audit @todo and FIXME for security issues
13 - the "break loader" and valid/invalid message tests are all disabled;
14 they need to be fixed and re-enabled with the new message args stuff.
15 I think I want to drop the .message files thing and just have code
16 that generates messages, more like the tests for
17 dbus-marshal-recursive.c (this is mostly done now, just needs some
20 - just before 1.0, try a HAVE_INT64=0 build and be sure it runs
22 - publish the introspection dtd at its URL
24 - fix locking on DBusPendingCall
26 - dbus_connection_open() is like dbus_bus_get() in that it returns a shared
27 connection; it needs the corresponding fix to hold a strong reference to
30 - _dbus_bus_check_connection_and_unref does not do proper locking and
31 doesn't handle all the shared connections, e.g. DBUS_BUS_STARTER
33 - for both the dbus-bus.c shared connections and dbus_connection_open()
34 shared connections, it is probably appropriate to warn() if someone
35 calls close() on them ; essentially shared connections are not closeable
36 because it's unclear who would do the closing and when, short of
39 Important for 1.0 GLib Bindings
42 - Test point-to-point mode
44 - Add support for getting sender
46 - format_version in the object info doesn't look like it's handled correctly. The creator
47 of the object info should specify some fixed number per struct version; the library
48 should handle only specific numbers it knows about. There's no assumption that all
49 numbers >= the given one are compatible. The idea is that new versions of the lib
50 can offer totally different object info structs, but old versions
53 Important for 1.0 Python bindings
58 - Fix removing of signals from the match tree
60 - Fix refcounting and userdata lifecycles
62 - Write a generic mainloop
67 - protocol version in each message is pretty silly
72 - if the GUID is obtained only during authentication, not in the address,
73 we could still share the connection
75 - Allow a dbus_g_proxy_to_string()/g_object_to_string() that
76 would convert the proxy to an "IOR" and dbus_g_proxy_from_string()
77 that would decode; using these, dbus-glib users could avoid
78 DBusConnection entirely. Of course the same applies to other kinds
79 of binding. This would use dbus_connection_open()'s connection-sharing
80 feature to avoid massive proliferation of connections.
82 - DBusWatchList/TimeoutList duplicate a lot of code, as do
83 protected_change_watch/protected_change_timeout in dbus-connection.c
84 and dbus-server.c. This could all be mopped up, cut-and-paste
85 fixed, code size reduced.
87 - change .service files to allow Names=list in addition to Name=string
89 - The message bus internal code still says "service" for
90 "name", "base service" for "unique name", "activate" for
91 "start"; would be nice to clean up.
93 - Property list feature on message bus (list of properties associated
94 with a connection). May also include message matching rules
95 that involve the properties of the source or destination
98 - Disconnecting the remote end on invalid UTF-8 is probably not a good
99 idea. The definition of "valid" is slightly fuzzy. I think it might
100 be better to just silently "fix" the UTF-8, or perhaps return an error.
102 - build and install the Doxygen manual in Makefile when --enable-docs
104 - if you send the same message to multiple connections, the serial number
105 will only be right for one of them. Probably need to just write() the serial
106 number, rather than putting it in the DBusMessage, or something.
108 - perhaps the bus driver should have properties that reflect attributes
109 of the session, such as hostname, architecture, operating system,
110 etc. Could be useful for code that wants to special-case behavior
111 for a particular host or class of hosts, for example.
113 - currently the security policy stuff for messages to/from
114 the bus driver is kind of strange; basically it's hardcoded that
115 you can always talk to the driver, but the default config file
116 has rules for it anyway, or something. it's conceptually
117 screwy at the moment.
119 - when making a method call, if the call serial were globally unique,
120 we could forward the call serial along with any method calls made
121 as a result of the first method call, and allow reentrancy that was
122 strictly part of the call stack of said method call. But I don't
123 really see how to do this without making the user pass around the
124 call serial to all method calls all the time, or disallowing
127 If done post 1.0 will probably be an optional/ugly-API type
130 - I don't want to introduce DBusObject, but refcounting and object
131 data could still be factored out into an internal "base class"
134 - Keep convenience wrappers in sync with bus methods
136 - document the auth protocol as a set of states and transitions, and
137 then reimplement it in those terms
139 - recursive dispatch, see dbus_connection_dispatch()
141 - do we need per-display activation; if so I'd like to do this by setting a
142 "display ID" property on screen 0, with a GUID, and keying activation by
143 said GUID. Otherwise you get all kinds of unrobust
144 string/hostname-based mess. per-screen is then done by appending screen number
145 to the display. If displays have a deterministic ID like this, you can
146 do per-display by simply including GUID in the service name.
148 - optimization and profiling!
150 - Match rules aren't in the spec (probably a lot of methods on the bus
156 - look into supporting the concept of a "connection" generically