[riot-notifications] [RIOT-OS/RIOT] Proposal: eSAUL - Extended Sensor Actuator Uber Layer (#14121)

chrysn notifications at github.com
Tue May 26 13:21:25 CEST 2020


I'm still not convinced the message bus is the right way to distribute those events -- with SAUL the application won't know the board's sensors' update rates and can't guarantee it will process all events without overflow.

In the concrete case of a saul_gcoap server, when there are two observations (say, on a fast temperature scanner and a slow humidity scanner), the thread that sends the notification will spend lots of time waiting for permission to send data. If it's messages that are coming in, it will need to be built in such a way that it can always process the messages inbetween and convert them to its own "this observation needs notification" flags.

The event approach sounds more practical to me -- the subscriber would allocate an event, pass that to the eSAUL thread, and that thread can fire the event (which would not block, and repeated calls before fetched don't do any harm). For eSAUL to support multiple listeners on a sensor, the allocated event would need to be prefixed by an eSAUL header that allows LL'ing the listeners together.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/14121#issuecomment-633964534
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200526/1022c4bd/attachment.htm>


More information about the notifications mailing list