Overall event/callback priority

[Anonymous]

Hi,

I have a question with respect to event/callback priority.

When using the WICED environment in combination with the BCM2073x family, the entire application is somewhat event driven.  You register a lot of callback functions and start executing a lot of functionality LE Stack event driven.

-I'm wondering if there is a kind of priority related to these events

-Are all events 100% guaranteed and always guaranteed to be received in the same order?

-Is it for instance possible, if the BCM connects to a peer device and quickly disconnects again, that events might be swapped or even disgarded/overruled?

-Is there a kind of flowchart/diagram that indicates the events and the guaranteed order in which they will be received?

Thanks in advance for your input on this subject.

Hans

[MichaelF_56]

Callbacks are serialized and run within the application thread with the same priority.

Unfortunately, threads cannot be created or destroyed (Re: threads - how to create/destroy them?), nor can any events/callbacks within the thread be prioritized (Callback priority).

There is however a way to Sending asynchronous event callback, which may be helpful.