summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Olbrich <m.olbrich@pengutronix.de>2010-05-27 20:20:50 +0200
committerMichael Olbrich <m.olbrich@pengutronix.de>2010-06-03 17:08:10 +0200
commitd481c0ef0cc7c81e05a002c3de7fa1dd44dc17f1 (patch)
treec0f8b26aa2318ea70fe4b2d0f79f844fe884d08b
parentc356cffea9504ae9ed657bb5b47e7baf27425fb4 (diff)
downloadjson-dbus-bridge-d481c0ef0cc7c81e05a002c3de7fa1dd44dc17f1.tar.gz
json-dbus-bridge-d481c0ef0cc7c81e05a002c3de7fa1dd44dc17f1.tar.xz
[TODO] extend
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
-rw-r--r--TODO12
1 files changed, 12 insertions, 0 deletions
diff --git a/TODO b/TODO
index 1aa6ce1..fb9db44 100644
--- a/TODO
+++ b/TODO
@@ -16,4 +16,16 @@ TODO
- how to avoid denial of service issues?
[ ] D-Bus dictionaries with non-string keys
+ - how to map these?
+ - "[[key, value], [key, value]]"?
+ - JSON object and use the string prepresentation of the key
+
+[ ] calculate the D-Bus parameter signature
+ - It can be derived from the introspection XML and then cached.
+ - This could happen on demand on the bridge, or on the client.
+
+[ ] dynamically create bindings from the introspection XML
+ - a qooxdoo class that created objects for a service.
+ - with functions for each D-Bus message
+ - events/listeners for signals (?)