diff options
author | 2019-07-16 23:39:27 +0200 | |
---|---|---|
committer | 2019-07-18 15:38:02 +0200 | |
commit | 6dfeafe7e4fa582b3db3f950136bc97f8611fc6d (patch) | |
tree | 62386661fe495dd8992260c89e09757326450edc /docs/annexes.md | |
parent | 5b5968815dc672467f40ed6b49f05a590bdb8b4d (diff) |
Tag broadcasted events with UUID and hop
When API have mutual dependencies, leading to
loops in dependecies, broadcasting an event
never ends because of the loop (see SPEC-2625).
To avoid that weird flood of events, a unic
identifier (UUID) is attached to broadcasted
event and a tiny memory records previously
broadcasted events to avoid re-sending an
already sent event.
The size of the memory can be set using the
macro variable EVENT_BROADCAST_MEMORY_COUNT
whose default value is 8. It can be reduced
to 0.
An other mecanism is added to limit the count
of hops that a broadcasted event can do. That
count can be set using the macro variable
EVENT_BROADCAST_HOP_MAX whose default value
is 10.
Bug-AGL: SPEC-2625
Change-Id: I29550a8a5c8f5e2ffb20edc3330357a1e870c0e2
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
Diffstat (limited to 'docs/annexes.md')
0 files changed, 0 insertions, 0 deletions