<p></p>
<blockquote>
<p>My concern about messages is what's happening when queues overflow.</p>
</blockquote>
<p>this.</p>
<p>May I suggest an extension to <code>sys/event</code>, where an event source (eg, sensor) has "event hooks", a list of events (event_t) that it just executes in sequence?</p>
<p>A list of events is just one pointer, as for msg_queues. But with an event, the user would have full control on what happens if the event gets triggered. Even sending a message is possible, or forwarding the event to another event_queue to process it in a different context.</p>
<blockquote>
<p>I think we should do the same here: Implement only one IPC mechanism that fits the standard use case best. If more are indeed needed, those mechanisms can provided as utility functions on top.</p>
</blockquote>
<p>yup.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/RIOT-OS/RIOT/issues/14121#issuecomment-633622922">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABE7WYHHP75WBWQTEYEO6RDRTKFDNANCNFSM4NIOMK5Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/ABE7WYF4X5CGEMERZNSZ6H3RTKFDNA5CNFSM4NIOMK52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEXCFDCQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/RIOT-OS/RIOT/issues/14121#issuecomment-633622922",
"url": "https://github.com/RIOT-OS/RIOT/issues/14121#issuecomment-633622922",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>