mcom
[Interface specifications]
Collaboration diagram for mcom:
|
Detailed Description
Client - client communication.
- Deprecated:
- Most of the functionality of this interface can be achieved through the opaque interface.
mcom interface is designed for exchanging information between clients. A client sends a message of a given "type" and "channel". This device stores adds the message to that channel's stack. A second client can then request data of a given "type" and "channel". Push, Pop, Read, and Clear operations are defined, but their semantics can vary, based on the stack discipline of the underlying driver. For example, the lifomcom (deprecated) driver enforces a last-in-first-out stack.
- Todo:
- Is this interface used and/or needed any more?
| #define | PLAYER_MCOM_REQ_PUSH 1 |
| request ids | |
| #define | PLAYER_MCOM_REQ_POP 2 |
| request ids | |
| #define | PLAYER_MCOM_REQ_READ 3 |
| request ids | |
| #define | PLAYER_MCOM_REQ_CLEAR 4 |
| request ids | |
| #define | PLAYER_MCOM_REQ_SET_CAPACITY 5 |
| request ids | |
| #define | MCOM_EMPTY_STRING "(EMPTY)" |
| returns this if empty | |
| typedef player_mcom_data | player_mcom_data_t |
| A piece of data. | |
| typedef player_mcom_config | player_mcom_config_t |
| Configuration request to the device. | |
| typedef player_mcom_return | player_mcom_return_t |
| Configuration reply from the device. |