-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
-
- - Audit @todo and FIXME for security issues
-
- - 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
-