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