blob: fb9db4419807fe3259b9869c5c8296ed41443781 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
TODO
====
[ ] unit tests
- via web server
- standalone test application
[ ] D-Bus structs
- There are no structs in JSON. Maybe an array and the type from the
parameter signature.
[ ] D-Bus signals
- bridge need to save a state for each client
- attach received signals to the state
- client can fetch signals with a special call (?)
- 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 (?)
|
