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

Marian Buschsieweke notifications at github.com
Tue May 26 15:15:03 CEST 2020


> 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).

I don't understand the semantic difference you see. A message is only delivered to a subscriber if:

a) The subscriber is currently blocked with receiving a message. (Thus, ready for the event)
b) The subscriber set up an message queue and there is still free space for at least one message.

So a subscriber not ready to process the next event would just not miss the message. This is semantically completely equivalent to what @chrysn suggested, isn't it?

Out of those two options, I see no reason to reinvent the wheel rather than just using the message bus. 

-- 
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-634017258
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200526/c47aa99c/attachment.htm>


More information about the notifications mailing list