summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorJohn (J5) Palmieri <johnp@redhat.com>2006-07-07 19:42:56 +0000
committerJohn (J5) Palmieri <johnp@redhat.com>2006-07-07 19:42:56 +0000
commit50f88a0322cee156a5d9737f0987e57b964606cc (patch)
tree6db31d41f4bbd27167e03654577db84cf36145ad /doc
parent84e55065ea9bef999f068de65c3eed0c9cc42fac (diff)
* dbus/dbus-connection.c (dbus_connection_close): removed deprecated
function (dbus_connection_dispatch): On disconnect unref any shared connections * dbus/dbus-bus.c (_dbus_bus_check_connection_and_unref): new function for cleaning up shared connections on disconnect (internal_bus_get): get a hard refrence to shared connections when they are created * doc/TODO: Remove items which are no longer relevent or have been fixed Split 1.0 todo items with a 0.90 freeze todo list
Diffstat (limited to 'doc')
-rw-r--r--doc/TODO36
1 files changed, 12 insertions, 24 deletions
diff --git a/doc/TODO b/doc/TODO
index 1b75985b..6ae67d1c 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,3 +1,15 @@
+Important for 0.90 freeze
+===
+
+- Audit @todo and FIXME for security issues that require API/ABI changes
+
+- dbus-pending-call.c has some API and thread safety issues to review.
+ DBusPendingCall is used from multiple threads with no locks.
+ Either DBusConnection's lock has to protect all associated pending
+ call (means pending->connection can't ever be set to null) or
+ or DBusPendingCall needs its own lock
+ http://lists.freedesktop.org/archives/dbus/2006-June/004945.html
+
Important for 1.0
===
@@ -8,8 +20,6 @@ Important for 1.0
locks. Fixes the recursive deadlock. See the @todo for more
and this thread: http://lists.freedesktop.org/archives/dbus/2006-February/004128.html
- - Remove all deprecated functions
-
- Audit @todo and FIXME for security issues
- the "break loader" and valid/invalid message tests are all disabled;
@@ -21,30 +31,8 @@ Important for 1.0
- just before 1.0, try a HAVE_INT64=0 build and be sure it runs
- - dbus-pending-call.c has some API and thread safety issues to review.
- DBusPendingCall is used from multiple threads with no locks.
- Either DBusConnection's lock has to protect all associated pending
- call (means pending->connection can't ever be set to null) or
- or DBusPendingCall needs its own lock
- http://lists.freedesktop.org/archives/dbus/2006-June/004945.html
-
- - Add test harness for selinux allow/deny cf. this message
- http://lists.freedesktop.org/archives/dbus/2005-April/002506.html
-
- publish the introspection dtd at its URL
- - RequestName flags seem a bit strange; see the docs for dbus_bus_request_name()
- and think about use cases in better detail.
- Proposal on list:
- http://lists.freedesktop.org/archives/dbus/2005-August/003207.html
-
- Kind of a major API change, but seems high-value.
-
- - dbus_bus_get() should hold a strong reference associated with the "connected"
- state (i.e. libdbus drops its reference when the connection disconnects,
- and sets its internal connection variable to null).
- See http://lists.freedesktop.org/archives/dbus/2006-May/004806.html
-
Important for 1.0 GLib Bindings
===