afb-evt: send events in separate job 67/21867/1
authorJose Bollo <jose.bollo@iot.bzh>
Thu, 11 Jul 2019 16:20:23 +0000 (18:20 +0200)
committerJosé Bollo <jose.bollo@iot.bzh>
Fri, 12 Jul 2019 14:07:37 +0000 (16:07 +0200)
commit919445036879bb7681cd19582a899ea43609c8a3
treef81ef125d50a27111d23373800b3bfb8700c50fd
parent14b401595576394f6d17aeddd6c172a445e30757
afb-evt: send events in separate job

Sending events in the context of the calling process
had the consequence that the ordering of the messages
had to be removed (see SPEC-2215 & SPEC-2219). This
was not good by nature and lead to issues SPEC-2542
and SPEC-2599.

Sending events in the context of the calling process
also implies to delay the calling process.

For this reasons, sending events is now done in an
other jobs. For that reason, the count of allowed
pending jobs is increased to 100 (was 50).

Bug-AGL: SPEC-2215
Bug-AGL: SPEC-2219
Bug-AGL: SPEC-2542
Bug-AGL: SPEC-2599

Change-Id: I5b56d952cc187b65ad6eb9344ad74e5e8d3b7540
Signed-off-by: Jose Bollo <jose.bollo@iot.bzh>
docs/reference-v3/func-api.md
docs/reference-v3/func-event.md
include/afb/afb-daemon-v1.h
include/afb/afb-daemon-v2.h
include/afb/afb-event-x2.h
src/afb-evt.c
src/main-afb-daemon.c