2 - How we will handle DCOP needs sorting out. Among other things, we
3 need to check that service and service-ownership semantics map to DCOP
6 - Activation needs some careful additional thinking-through.
8 - Property list feature on message bus (list of properties associated
9 with a connection). May also include message matching rules
10 that involve the properties of the source or destination
13 - Automatic service activation, should probably be done through a message flag.
15 - Disconnecting the remote end on invalid UTF-8 is probably not a good
16 idea. The definitiion of "valid" is slightly fuzzy. I think it might
17 be better to just silently "fix" the UTF-8, or perhaps return an error.
19 Owen says we should only validate the UTF-8 on dbus_message_get_string()
20 (changing get_string to have an error return, and allowing a type error
23 - The convenience functions in dbus-bus.h should perhaps have
24 the signatures that they would have if they were autogenerated
25 stubs. e.g. the acquire service function. We should also evaluate
26 which of these functions to include, in light of the fact that
27 GLib/Qt native stubs will probably also exist.
29 - assorted _-prefixed symbols in libdbus aren't actually used by
30 libdbus, only by the message bus. These bloat up the library
31 size. Not sure how to fix, really.
33 - build and install the Doxygen manual in Makefile when --enable-docs
35 - if you send the same message to multiple connections, the serial number
36 will only be right for one of them. Probably need to just write() the serial
37 number, rather than putting it in the DBusMessage, or something.
39 - perhaps the bus driver should have properties that reflect attributes
40 of the session, such as hostname, architecture, operating system,
41 etc. Could be useful for code that wants to special-case behavior
42 for a particular host or class of hosts, for example.
44 - currently the security policy stuff for messages to/from
45 the bus driver is kind of strange; basically it's hardcoded that
46 you can always talk to the driver, but the default config file
47 has rules for it anyway, or something. it's conceptually
50 - <limit> elements are not merged in from included configuration
51 files; they have to be in the toplevel file. when loading
52 a child file, we could just init its DBusLimits from the parent,
53 then after parsing copy its DBusLimits back to the parent
55 - when making a method call, if the call serial were globally unique,
56 we could forward the call serial along with any method calls made
57 as a result of the first method call, and allow reentrancy that was
58 strictly part of the call stack of said method call. But I don't
59 really see how to do this without making the user pass around the
60 call serial to all method calls all the time, or disallowing
63 - the invalid messages in the test suite are all useless because
64 they are invalid for the wrong reasons due to protocol changes.
65 (Consider extending test suite to validate that they are
66 invalid for right reason, e.g. an "INVALID_ERROR Foo" line
69 - I don't want to introduce DBusObject, but refcounting and object
70 data could still be factored out into an internal "base class"
73 - modify the auth protocol to also support other initial-handshake
76 - document the auth protocol as a set of states and transitions, and
77 then reimplement it in those terms
79 - dbus_gproxy or dbus_g_proxy?
81 - add dbus_message_has_path(), maybe has_member/interface
83 - re_align_field_recurse() in dbus-message.c is broken because it
84 crashes on some types of header field values. security problem.
86 - the system daemon has to be able to reload changes to the
87 security policy without restarting, because apps won't
88 be coded to handle it restarting
90 - modify the wire protocol to keep the args signature separate
91 from the args themselves. Make the name of TYPE_CUSTOM part
92 of the type signature, rather than part of the value.
93 Then you have the full typecheck in a single string.
95 - dbus_message_iter_init_array_iterator has "iter" and "iterator"
96 in the same function name
98 - the GLib bindings varargs take DBUS_TYPE_WHATEVER and
99 return stuff allocated with dbus_malloc(); should this
100 be made more "G" at some expense in code duplication?
101 You also still have to use some D-BUS functions such as
102 dbus_message_get_args() which takes a DBusError.
103 Probably we need to either fully encapsulate and hide
104 dbus/dbus.h, or encapsulate it slightly less e.g. no
105 GError. Or maybe it's as simple as "never return dbus_malloc()
106 memory" and just fully encapsulate the get_args() type of
109 - need to define bus behavior if you send a message to
110 yourself; is it an error, or allowed? If allowed,
111 we need to have a test for it in the test suite.
113 - the max_replies_per_connection resource limit isn't implemented
115 - array lengths should probably be returned as size_t rather than int
116 (though they are kind of a pita to pass in as size_t with the
117 varargs, so maybe not - what does glib do with g_object_get()?)
119 - the varargs dbus_message_get_args() needs to support OBJECT_PATH
120 and OBJECT_PATH_ARRAY
122 - recursive dispatch, see dbus_connection_dispatch()
124 - the auth protocol may as well use hex encoding instead of
125 base64, then we can dump the base64 implementation and
128 - rename HEADER_FIELD_SERVICE -> HEADER_FIELD_DESTINATION
129 and HEADER_FIELD_SENDER_SERVICE -> HEADER_FIELD_SENDER
130 for both dbus-protocol.h and in the spec