![]() |
![]() |
![]() |
![]() |
Get the next queued MME event
#include <mme/mme.h> int mme_get_event( mme_hdl_t *hdl, mme_event_t **mme_event );
mme
The function mme_get_event() allows you to determine when your client application receives events. It retrieves events from the event queue, and places event information in the mme_event_t data structure. This information includes the event:
Events are associated with an MME connection handle mme_hdl_t; they cannot be cleared by the client application.
The MME does not automatically place events in the event queue. You must use the function mme_register_for_events() to register for the types of events your client application needs to receive. Registration is typically done immediately after connection.
When the client application is registered for one or more type of event, the MME places these event types in an event queue and sends the relevant sigevent to the client application. Based on the sigevent, the client can decide to call mme_get_event() to retrieve the event.
![]() |
A call to mme_get_event() invalidates any data that was in the mme_event_t before the call was made. If the client application needs to keep event information longer than the next call to mme_get_event(), it must copy the event before calling mme_get_event(). |
For more information about registering for events, see “Registering for events” in the chapter Starting Up and Connecting to the MME of the MME Developer's Guide, and mme_register_for_events().
If your client application does not register for events before it calls mme_get_event(), the event queue will be empty. If there are no events in the event queue mme_event_type_t will be set to MME_EVENT_NONE.
For more information about these data structures, see the relevant sections in the chapter MME Events.
None delivered.
This function doesn't perform any validations, and blocks only on internal event structures. It doesn't block on processes external to the MME, such as qdb or io-media.
QNX Neutrino
Safety: | |
---|---|
Interrupt handler | No |
Signal handler | No |
Thread | Yes |
mme_connect(), mme_disconnect(), mme_register_for_events(), MME Events, “Registering for events” in the MME Developer's Guide
![]() |
![]() |
![]() |
![]() |