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