[En-Nut-Discussion] Another set of eyes

[Ralph Mason]

Days of puzzling and I just needed to read the documentation more clearly.

Anyhow, this is why I call it Async from user code.

My Message que supports a broadcast to all listeners.  This allows simple
IPC and only interested threads need process the broadcast.

The broadcasting thread clearly doesn't want to be context switched until
All the ques have been posted to, otherwise a lower priority thread will run
first.

Also a thread may want to put a message in a Que but not context switch.

I guess that anytime there is more than one event to be triggered by a
thread it is possible that it may want to do it Async.  Eg, you have some
function that notes a state and sets an event, however you would rather the
calling thread completed before it context switched.

Perhaps functions that are expected to be called with interrupts disabled
could be  FuncI eg NutPostAsyncI, or some other method that clearly points
out the folly of the callers ways.

Thanks,
Ralph

> -----Original Message-----
> From: en-nut-discussion-admin at egnite.de
> [mailto:en-nut-discussion-admin at egnite.de]On Behalf Of Harald Kipp
> Sent: Tuesday, 22 July 2003 8:09
> To: en-nut-discussion at egnite.de
> Subject: RE: [En-Nut-Discussion] Another set of eyes
>
>
> Ralph,
>
> It is cleared stated in a note, that
>
>   * \note It is save to call this function from within an interrupt
>   *       handler. In any case interrupts must be disabled when
>   *       calling this function.
>   *
>
> NutEventPostAsync is intended for use by interrupt routines and
> may be used too by time critical routines. Both would have
> interrupts disabled.
>
> Can you (or anybody else) provide an example, where "normal"
> application code must use NutEventPostAsync instead of
> NutEventPost?
>
> Harald
>
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo/en-nut-discussion
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.491 / Virus Database: 290 - Release Date: 18/06/2003
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.491 / Virus Database: 290 - Release Date: 18/06/2003