|
Detailed Description
The 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 driver enforces a last-in-first-out stack.
This interface returns no data and accepts no commands.
Define Documentation
#define MCOM_DATA_LEN 128
|
|
|
size of the data field in messages |
#define MCOM_DATA_BUFFER_SIZE 0
|
|
|
number of buffers to keep per channel |
#define MCOM_CHANNEL_LEN 8
|
|
#define MCOM_EMPTY_STRING "(EMPTY)"
|
|
#define PLAYER_MCOM_PUSH_REQ 0
|
|
#define PLAYER_MCOM_POP_REQ 1
|
|
#define PLAYER_MCOM_READ_REQ 2
|
|
#define PLAYER_MCOM_CLEAR_REQ 3
|
|
#define PLAYER_MCOM_SET_CAPACITY_REQ 4
|
|
Typedef Documentation
|
Configuration request: Config requests sent to server.
|
|
Configuration reply from server.
|
Generated on Tue May 3 14:16:10 2005 for Player by 1.3.6
|