Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I56f4f6aebe673363c8b07c55f68ebbb1362b04fc
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: Ie7ebccb02b42e91457df3bdbf2a6f037b248400e
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: I354649f885daf89426f3b1612127045fdf1dedcc
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: Ic9e118df2bede1fefbb591f8ae7887266b7324ca
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
This new version allows to subscribe a client for
an event.
The event should first be created for the API
(the API's prefix is added) using 'afb_daemon_make_event'.
After that, plugins can subscribe or unsubscribe their
clients (identified through requests) to the events that
it generates. See 'afb_req_subscribe' and 'afb_req_unsubscribe'.
Events created by 'afb_daemon_make_event' can be widely
broadcasted using 'afb_event_broadcast' or pushed only to
suscribers using 'afb_event_push'.
Events can be destroyed using 'afb_event_drop'.
Change-Id: I7c0bed5e625c2052dcd81c6bfe960def1fa032f3
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|