-Important for 1.0
+Important for 1.2
===
- - Remove all deprecated functions
+ - System bus activation
- - Audit @todo and FIXME for security issues
+ - Windows port
- - the "break loader" and valid/invalid message tests are all disabled;
- they need to be fixed and re-enabled with the new message args stuff.
- I think I want to drop the .message files thing and just have code
- that generates messages, more like the tests for
- dbus-marshal-recursive.c (this is mostly done now, just needs some
- cleanup)
-
- - need to define bus behavior if you send a message to
- yourself; is it an error, or allowed? If allowed,
- we need to have a test for it in the test suite.
-
- - just before 1.0, try a HAVE_INT64=0 build and be sure it runs
+Important for 1.0 GLib Bindings
+===
- - dbus-pending-call.c has some API and thread safety issues to review
+ - Test point-to-point mode
- - Add test harness for selinux allow/deny cf. this message
- http://lists.freedesktop.org/archives/dbus/2005-April/002506.html
+ - Add support for getting sender
- - Add a test case for handling the Ping message
+ - format_version in the object info doesn't look like it's handled correctly. The creator
+ of the object info should specify some fixed number per struct version; the library
+ should handle only specific numbers it knows about. There's no assumption that all
+ numbers >= the given one are compatible. The idea is that new versions of the lib
+ can offer totally different object info structs, but old versions
+ keep working.
-Important for 1.0 GLib Bindings
+Important for 1.0 Python bindings
===
- - Annotations for "do not take ownership of this return value" on server
+ - Hammer down API
- - Support a{sv}
+ - Fix removing of signals from the match tree
- - Test point-to-point mode
+ - Fix refcounting and userdata lifecycles
- - Add support for getting sender
+ - Write a generic mainloop
Might as Well for 1.0
===
Can Be Post 1.0
===
+ - revamp dbus-launch a bit,
+ see http://lists.freedesktop.org/archives/dbus/2006-October/005906.html
+ for some thoughts.
+
+ - clean up the creds issue on *BSD's in dbus/dbus-sysdeps-unix.c.
+ They should work as is but we need to rearange it to make it
+ clearer which method is being used. configure.in should
+ be fixed up to make that decition.
+
+ - _dbus_connection_unref_unlocked() is essentially always broken because
+ the connection finalizer calls non-unlocked functions. One fix is to make
+ the finalizer run with the lock held, but since it calls out to the app that may
+ be pretty broken. More likely all the uses of unref_unlocked are just wrong.
+
- if the GUID is obtained only during authentication, not in the address,
we could still share the connection
data could still be factored out into an internal "base class"
perhaps.
+ - Keep convenience wrappers in sync with bus methods
+
- document the auth protocol as a set of states and transitions, and
then reimplement it in those terms
- optimization and profiling!
+ - Match rules aren't in the spec (probably a lot of methods on the bus
+ are not)
+
+ - the "break loader" and valid/invalid message tests are all disabled;
+ they need to be fixed and re-enabled with the new message args stuff.
+ I think I want to drop the .message files thing and just have code
+ that generates messages, more like the tests for
+ dbus-marshal-recursive.c (this is mostly done now, just needs some
+ cleanup)
+
+ - just before 1.0, try a HAVE_INT64=0 build and be sure it runs
+
+ - Windows port needs recursive mutexes
+
Should Be Post 1.0
===
- look into supporting the concept of a "connection" generically
+ (what does this TODO item mean?)
+
+ - test/name-test should be named test/with-bus or something like that
+
projects / platform / upstream / dbus.git / blobdiff