summaryrefslogtreecommitdiffstats
path: root/doc/TODO
diff options
context:
space:
mode:
authorHavoc Pennington <hp@redhat.com>2005-01-18 20:42:15 +0000
committerHavoc Pennington <hp@redhat.com>2005-01-18 20:42:15 +0000
commit8873c90f99303f9cc308f15f8d03e637911f5b9e (patch)
tree03e459881912388cc6c3759d91fb0cf75739a5a7 /doc/TODO
parent4fce285052c143296cd9e08a48de0175b5207853 (diff)
2005-01-18 Havoc Pennington <hp@redhat.com>
* Throughout, grand renaming to strip out the use of "service", just say "name" instead (or "bus name" when ambiguous). Did not change the internal code of the message bus itself, only the programmer-facing API and messages. * doc/dbus-specification.xml: further update the message bus section * bus/config-parser.c (all_are_equiv): fix bug using freed string in error case
Diffstat (limited to 'doc/TODO')
-rw-r--r--doc/TODO16
1 files changed, 10 insertions, 6 deletions
diff --git a/doc/TODO b/doc/TODO
index c688583e..eac3e50b 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,5 +1,7 @@
Important for 1.0
===
+
+ - change .service files to have Names=list rather than Name=string
- How we will handle DCOP needs sorting out. Among other things, we
need to check that service and service-ownership semantics map to DCOP
@@ -38,18 +40,14 @@ Important for 1.0
(though they are kind of a pita to pass in as size_t with the
varargs, so maybe not - what does glib do with g_object_get()?)
- - rename the service thing. unique service names (":1") and well-known
- ("org.foo.bar") should have different names probably; something like
- "address" for the unique and "alias" for the well-known, or
- "application id" for the unique and "common name" or "published
- name" for the well-known; not sure yet.
-
- things are broken now when mixing endianness, because DBusMessage
doesn't autoswap itself when you access a message of alternate
endian.
- add string array support back to append_args()
+ - auto-activate by default
+
Important for 1.0 GLib Bindings
===
@@ -71,6 +69,8 @@ Important for 1.0 GLib Bindings
so it can figure out how to invoke the callback, or we have to rely
on having introspection data.
+ - DBusGProxy doesn't emit "destroy" when it should
+
Might as Well for 1.0
===
@@ -90,6 +90,10 @@ Might as Well for 1.0
Can Be Post 1.0
===
+ - The message bus internal code still says "service" for
+ "name", "base service" for "unique name", "activate" for
+ "start"; would be nice to clean up.
+
- 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