X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=doc%2FTODO;h=eb4e797ff6fcc61919e9194c3dc75605706dac45;hb=b54067510f80d2e570c1afdb4b17ee4d0b7c57ed;hp=b46ac329cd220b0ff7007280cc6a078d63e0b9cb;hpb=88f69757b93c7112447b97868c7dbde69dc00caa;p=platform%2Fupstream%2Fdbus.git

diff --git a/doc/TODO b/doc/TODO
index b46ac32..eb4e797 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,42 +1,9 @@
-Important for 1.0
+Important for 1.2
 ===
 
- - add a new return code from dbus_connection_dispatch() called 
-   IN_PROGRESS or RECURSED or something, indicating that DATA_REMAINS
-   but another dispatch is in progress, so we can't dispatch at 
-   this time. OR maybe just switch to recursive locks for the dispatch 
-   locks. Fixes the recursive deadlock. See the @todo for more
-   and this thread: http://lists.freedesktop.org/archives/dbus/2006-February/004128.html
+ - System bus activation
 
- - Take a look at the issues marked @todo 1.0 or FIXME 1.0.  Ones with
-   Question marks at the ends either need clarification or are not 
-   really needed for 1.0 but would be nice.
-
- - 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
-
- - publish the introspection dtd at its URL
-
- - fix locking on DBusPendingCall
-
- - dbus_connection_open() is like dbus_bus_get() in that it returns a shared
-   connection; it needs the corresponding fix to hold a strong reference to 
-   these connections.
-
- - _dbus_bus_check_connection_and_unref does not do proper locking and 
-   doesn't handle all the shared connections, e.g. DBUS_BUS_STARTER
-
- - for both the dbus-bus.c shared connections and dbus_connection_open() 
-   shared connections, it is probably appropriate to warn() if someone 
-   calls close() on them ; essentially shared connections are not closeable
-   because it's unclear who would do the closing and when, short of 
-   dbus_shutdown()
+ - Windows port
 
 Important for 1.0 GLib Bindings
 ===
@@ -71,6 +38,20 @@ 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
 
@@ -152,8 +133,23 @@ Can Be Post 1.0
  - 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
+