diff options
author | clement benier <clement.benier@iot.bzh> | 2018-06-19 11:37:45 +0200 |
---|---|---|
committer | cle©mentbeénier <clement.benier@iot.bzh> | 2018-06-21 14:23:38 +0200 |
commit | 1fc63a30ca5bd00f0f6c9805f0ff0c0c7ac29c1e (patch) | |
tree | 0c44ee83490a5d28e013d4789f5e0a8c3309d053 /README.md | |
parent | ac72aa8923906e2afc91b8bd6d483fc4ebcf39c9 (diff) |
context_set vs uid: remove json key uid and set context for afb_req
Remove the uid json argument and using afb_req_context_set/get to
identify client session.
Change-Id: Ib57f4443d20f4ee7cec9db17b6c6b81d6ca0e24c
Signed-off-by: clement benier <clement.benier@iot.bzh>
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 12 |
1 files changed, 7 insertions, 5 deletions
@@ -10,15 +10,14 @@ to get data from acceleration, gyroscope and electronic compass. As soon as a client subscribes to the agl-service-iiodevices binding, the binding gets values from sensors and send it to subscribers as events. Subscribers can choose their frequency and indicates what values they wants at -subscription. For now, subscribers have also to indicates an uid in order to -create differents events, if arguments differ between clients. +subscription. ## Verbs | Name | Description | JSON Parameters | |:-------------------|:--------------------------------------------|:--------------------------------------------------------------- | -| subscribe | subscribe to 9 axis events | *Request:* {"event": "accel", "uid": "X", "args":"xy", "frequency": "10" }| -| unsubscribe | unsubscribe to accelero events | *Request:* {"event": "accel", "uid": "X"} | +| subscribe | subscribe to 9 axis events | *Request:* {"event": "accel", "args":"xy", "frequency": "10" }| +| unsubscribe | unsubscribe to accelero events | *Request:* {"event": "accel" } | ## Events @@ -28,10 +27,13 @@ For now, there are 3 different events matching with the different available sens * "magn": is for gyroscope data * "anglvel": is for electronic compass data +## Frequency + +Frequency is in Hertz, if the frequency is not filled, events are triggered via file descriptor. + ## Remaining issues - Provide a json config file so that configures the device name and the channel name. -- Remove the uid json argument and using context_make to identify session and better handle events - Rework on channel structure and split it into client structure - Handle several values simultaneously, see trigger - Update it to other iiodevices |