The IC protocol is the description of messages exchanged between Interaction Controller (IC) end-points, specifically between a client and a server. This protocol is used by all Interaction Controller back-ends, except for the 'erl_plain' and 'erl_corba' back-ends. The IC protocol itself is embedded within the Erlang gen_server protocol.
In simpler terms, think of the IC protocol as the language clients and servers use to communicate within the Interaction Controller system. It defines the structure and meaning of the messages they send to each other.
Key Aspects of the IC Protocol
- Message Exchange: The primary function of the IC protocol is to define how clients and servers exchange messages.
- IC End-Points: This communication happens between IC end-points, which are essentially the client and server components of the IC system.
- Back-end Specificity: The IC protocol is valid for most IC back-ends, excluding 'erl_plain' and 'erl_corba'.
- Embedded within Erlang: The IC protocol is further embedded in the Erlang
gen_serverprotocol. This means it leverages the functionalities and structure provided by Erlang's general server behavior.
Example Scenario
Imagine a scenario where a client wants to retrieve some data from a server within the IC system. The process would look something like this:
- Client Request: The client formulates a request message according to the IC protocol. This message specifies what data the client needs.
- Server Reception: The server receives the client's message.
- Server Processing: The server processes the message based on the IC protocol's definition of the message structure and intended action.
- Server Response: The server then formulates a response message, again adhering to the IC protocol, containing the requested data (or an error message if the request could not be fulfilled).
- Client Reception: The client receives and interprets the server's response message according to the IC protocol.
This entire process is facilitated and defined by the IC protocol.
