Although event broker messages come in enough flavors to allow a task to carry out a variety of I/O operations through the event broker, the event broker's main function is to monitor events in user-interface devices and report the events to listening tasks. From a listener task's point of view, the process of event monitoring has the following steps:
Connecting to the event broker
Create a message port
Create a configuration message
Create a configuration block
Send the configuration message to the event broker
Receive the event broker's connection reply message
Monitoring events through the event broker
Wait for event messages on the allocated message port
Read an event message data block
Process event data block information (if desired)
Reply to the event broker for event message receipt
Changing configuration (if desired) or disconnecting from the event broker
Send a new configuration data structure to the event broker
Each of these steps use event broker data structures and message flavors.