Connection Machine Signal Pattern
Each signal is exposed to the outside systems as a Uniform interface. This section identifies the components of the uniform interface of an interaction.
Each signal or interaction is identified to the external system as a URI. Each time a signal is created it creates a Connection machine wide nonce or a unique namespace. The URI signal namespace is a hierarchical space. The name space consists of the following basic components, The structure of this signal URI namespace is
DomainName/ProcessName/PRocessID/Actionname/Sequenceid/(Tell or ASK).
| Signal component | Description |
| Domain Name | The top most name in the MasterKube system is the domain. A domain can refer to a different company. This way it is possible to have two companies or tenants to share a MasterKube Installation. |
| Process Name | An agent creates a new process, a new process id is created. This is unique number generated by MasterKube Connection Machine. |
| Process ID | An agent creates a new process, a new process id is created. This is unique number generated by MasterKube Connection Machine. |
| Action Name | The data in MasterKube is hidden. It is exposed only through signals. Each action gives the signature of the data that is exposed. Depending on the action name the appropriate data is exposed. If an action is tagged as hidden then it will not appear in the signal output. |
| Sequence ID | The sequence id ensures that the signal is unique. This is used to make sure only one interaction happens at any point in time. When an interaction happens on this signal, then a new number is generated. Right now this is a sequence number, but this can be changed to make an opaque numbering scheme to increase security. Each TELL or ASK operator creates a unique id. |
| (Tell or ASK) | Depending on the type of signal the appropriate TELL or ASK is shown here. |
