dbus/doc TODO,1.107,1.108
John Palmieri
johnp at kemper.freedesktop.org
Wed Sep 13 21:26:03 PDT 2006
- Previous message: dbus/dbus dbus-dataslot.c, 1.14, 1.15 dbus-list.c, 1.24,
1.25 dbus-threads-internal.h, 1.3, 1.4 dbus-threads.c, 1.28,
1.29 dbus-threads.h, 1.10, 1.11
- Next message: dbus/dbus dbus-server.c,1.45,1.46
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Update of /cvs/dbus/dbus/doc
In directory kemper:/tmp/cvs-serv3152/doc
Modified Files:
TODO
Log Message:
* dbus/dbus-threads.c: Allow recursive mutex's to be passed into
dbus_threads_init and be used by the dbus mutex functions to
avoid deadlocks.
* doc/TODO: Remove recursive mutex dbus_connection_dispatch TODO item
Index: TODO
===================================================================
RCS file: /cvs/dbus/dbus/doc/TODO,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -d -r1.107 -r1.108
--- TODO 6 Sep 2006 22:00:07 -0000 1.107
+++ TODO 14 Sep 2006 04:26:00 -0000 1.108
@@ -1,13 +1,6 @@
Important for 1.0
===
- - 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
-
- 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.
- Previous message: dbus/dbus dbus-dataslot.c, 1.14, 1.15 dbus-list.c, 1.24,
1.25 dbus-threads-internal.h, 1.3, 1.4 dbus-threads.c, 1.28,
1.29 dbus-threads.h, 1.10, 1.11
- Next message: dbus/dbus dbus-server.c,1.45,1.46
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the dbus-commit
mailing list