4 - support recursive locks in dbus_threads_init_default()
6 Important for 1.0 GLib Bindings
9 - Test point-to-point mode
11 - Add support for getting sender
13 - format_version in the object info doesn't look like it's handled correctly. The creator
14 of the object info should specify some fixed number per struct version; the library
15 should handle only specific numbers it knows about. There's no assumption that all
16 numbers >= the given one are compatible. The idea is that new versions of the lib
17 can offer totally different object info structs, but old versions
20 Important for 1.0 Python bindings
25 - Fix removing of signals from the match tree
27 - Fix refcounting and userdata lifecycles
29 - Write a generic mainloop
34 - protocol version in each message is pretty silly
39 - _dbus_connection_unref_unlocked() is essentially always broken because
40 the connection finalizer calls non-unlocked functions. One fix is to make
41 the finalizer run with the lock held, but since it calls out to the app that may
42 be pretty broken. More likely all the uses of unref_unlocked are just wrong.
44 - if the GUID is obtained only during authentication, not in the address,
45 we could still share the connection
47 - Allow a dbus_g_proxy_to_string()/g_object_to_string() that
48 would convert the proxy to an "IOR" and dbus_g_proxy_from_string()
49 that would decode; using these, dbus-glib users could avoid
50 DBusConnection entirely. Of course the same applies to other kinds
51 of binding. This would use dbus_connection_open()'s connection-sharing
52 feature to avoid massive proliferation of connections.
54 - DBusWatchList/TimeoutList duplicate a lot of code, as do
55 protected_change_watch/protected_change_timeout in dbus-connection.c
56 and dbus-server.c. This could all be mopped up, cut-and-paste
57 fixed, code size reduced.
59 - change .service files to allow Names=list in addition to Name=string
61 - The message bus internal code still says "service" for
62 "name", "base service" for "unique name", "activate" for
63 "start"; would be nice to clean up.
65 - Property list feature on message bus (list of properties associated
66 with a connection). May also include message matching rules
67 that involve the properties of the source or destination
70 - Disconnecting the remote end on invalid UTF-8 is probably not a good
71 idea. The definition of "valid" is slightly fuzzy. I think it might
72 be better to just silently "fix" the UTF-8, or perhaps return an error.
74 - build and install the Doxygen manual in Makefile when --enable-docs
76 - if you send the same message to multiple connections, the serial number
77 will only be right for one of them. Probably need to just write() the serial
78 number, rather than putting it in the DBusMessage, or something.
80 - perhaps the bus driver should have properties that reflect attributes
81 of the session, such as hostname, architecture, operating system,
82 etc. Could be useful for code that wants to special-case behavior
83 for a particular host or class of hosts, for example.
85 - currently the security policy stuff for messages to/from
86 the bus driver is kind of strange; basically it's hardcoded that
87 you can always talk to the driver, but the default config file
88 has rules for it anyway, or something. it's conceptually
91 - when making a method call, if the call serial were globally unique,
92 we could forward the call serial along with any method calls made
93 as a result of the first method call, and allow reentrancy that was
94 strictly part of the call stack of said method call. But I don't
95 really see how to do this without making the user pass around the
96 call serial to all method calls all the time, or disallowing
99 If done post 1.0 will probably be an optional/ugly-API type
102 - I don't want to introduce DBusObject, but refcounting and object
103 data could still be factored out into an internal "base class"
106 - Keep convenience wrappers in sync with bus methods
108 - document the auth protocol as a set of states and transitions, and
109 then reimplement it in those terms
111 - recursive dispatch, see dbus_connection_dispatch()
113 - do we need per-display activation; if so I'd like to do this by setting a
114 "display ID" property on screen 0, with a GUID, and keying activation by
115 said GUID. Otherwise you get all kinds of unrobust
116 string/hostname-based mess. per-screen is then done by appending screen number
117 to the display. If displays have a deterministic ID like this, you can
118 do per-display by simply including GUID in the service name.
120 - optimization and profiling!
122 - Match rules aren't in the spec (probably a lot of methods on the bus
125 - the "break loader" and valid/invalid message tests are all disabled;
126 they need to be fixed and re-enabled with the new message args stuff.
127 I think I want to drop the .message files thing and just have code
128 that generates messages, more like the tests for
129 dbus-marshal-recursive.c (this is mostly done now, just needs some
132 - just before 1.0, try a HAVE_INT64=0 build and be sure it runs
137 - look into supporting the concept of a "connection" generically
138 (what does this TODO item mean?)
140 - test/name-test should be named test/with-bus or something like that