4 - Audit @todo and FIXME for security issues
6 - The convenience functions in dbus-bus.h should perhaps have
7 the signatures that they would have if they were autogenerated
8 stubs. e.g. the acquire service function. We should also evaluate
9 which of these functions to include, in light of the fact that
10 GLib/Qt native stubs will probably also exist.
12 - the "break loader" and valid/invalid message tests are all disabled;
13 they need to be fixed and re-enabled with the new message args stuff.
14 I think I want to drop the .message files thing and just have code
15 that generates messages, more like the tests for
16 dbus-marshal-recursive.c (this is mostly done now, just needs some
19 - need to define bus behavior if you send a message to
20 yourself; is it an error, or allowed? If allowed,
21 we need to have a test for it in the test suite.
23 - validate dict entry number of fields
25 - just before 1.0, try a HAVE_INT64=0 build and be sure it runs
27 - in dbus-keyring.c, enforce that the keyring dir is not
28 world readable/writable
32 - fix introspection format to handle all signatures
34 Important for 1.0 GLib Bindings
37 - finish dbus-glib-tool support for adding introspection
38 data to GObject and autoexporting GObject using same
40 - Need to make sure that dbus-glib.h never returns any
41 dbus_malloc() memory, only g_malloc().
42 dbus_g_proxy_end_call() is the major offender.
44 - DBusGProxy doesn't emit "destroy" when it should
49 - add dbus_message_has_path(), maybe has_member/interface
51 - connection_open/connection_disconnect lacks symmetry, open/close
54 - protocol version in each message is pretty silly
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 - document the auth protocol as a set of states and transitions, and
107 then reimplement it in those terms
109 - recursive dispatch, see dbus_connection_dispatch()
111 - do we need per-display activation; if so I'd like to do this by setting a
112 "display ID" property on screen 0, with a GUID, and keying activation by
113 said GUID. Otherwise you get all kinds of unrobust
114 string/hostname-based mess. per-screen is then done by appending screen number
115 to the display. If displays have a deterministic ID like this, you can
116 do per-display by simply including GUID in the service name.
118 - optimization and profiling!