summaryrefslogtreecommitdiffstats
path: root/doc/TODO
diff options
context:
space:
mode:
authorHavoc Pennington <hp@redhat.com>2003-03-18 23:22:12 +0000
committerHavoc Pennington <hp@redhat.com>2003-03-18 23:22:12 +0000
commitb052524195a48f9b5e55cc7a456e0e1cc318f98b (patch)
treebeafc6f1d78abbc97108724bee594e28f7def0cc /doc/TODO
parentd04cc0dc291f90afddd9075dc5df6470d3f01870 (diff)
2003-03-18 Havoc Pennington <hp@redhat.com>
* doc/TODO: some notes on high-level todo items. Little nitpick stuff is all in @todo, so no need to add it here. * doc/config-file.txt: some notes on how config file might look
Diffstat (limited to 'doc/TODO')
-rw-r--r--doc/TODO41
1 files changed, 41 insertions, 0 deletions
diff --git a/doc/TODO b/doc/TODO
new file mode 100644
index 00000000..dffb7389
--- /dev/null
+++ b/doc/TODO
@@ -0,0 +1,41 @@
+
+ - Service and message names should be more carefully restricted;
+ they should have a max length, may not be an empty string,
+ and perhaps should not be allowed to be a glob such as "*" since
+ the config file could conveniently use such notation.
+
+ Suggest requiring length > 0, length < max,
+ name contains at least one ".", no initial ".", and valid UTF-8.
+ That would prohibit plain "*" but not "foo.bar.baz.operator*"
+
+ For maximum convenience from all programming languages, we could go
+ further and just categorically ban nearly all non-alphanumeric
+ characters.
+
+ - Message matching rules (so broadcasts can be filtered) need sorting
+ out.
+
+ - How we will handle DCOP needs sorting out. Among other things, we
+ need to check that service and service-ownership semantics map to DCOP
+ reasonably well.
+
+ - Activation needs some careful additional thinking-through.
+
+ - Recursive/composite/etc. types and associated API, see mailing list.
+
+ - dbus-bus.h should contain convenience API for connecting to system
+ and login-session message buses (automatically handling env
+ variables etc.)
+
+ - Configuration file (working on that now)
+
+ - Property list feature on message bus (list of properties associated
+ with a connection). May also include message matching rules
+ that involve the properties of the source or destination
+ connection.
+
+ - Implement all the needed resource limits to keep clients from
+ killing the message bus.
+
+
+