Binding (2)

Bindings (the binding table entries) can be stored either on the network Co-ordinator or locally on the node generating the source output cluster. Depending on where the binding information is stored, transmission of the cluster information from source to destination is direct or indirect.

Direct (or Local) Binding

In the case of direct or local binding, the binding table is stored on the node. Therefore, when new output cluster information is to be transmitted:

All entries containing the cluster ID are found locally
A message containing the new cluster information is generated for each the entry in the table
For each message generated, the node puts the destination address and endpoint information from the table entry into the message, and the message is sent directly to the destination application using the most appropriate path in the network

Direct binding

Indirect (or Co-ordinator) Binding

In the case of indirect or co-ordinator binding, the binding table is stored on the network Co-ordinator. Therefore, messages must be sent via the Co-ordinator. When the output cluster information changes on the source node:

A message containing the new information and the source application address (network address and endpoint) is sent to the network Co-ordinator
The Co-ordinator finds all entries in its binding table containing the source cluster and application address, and generates a message replicating the cluster information it received for each entry found
For each message, it inserts the destination address and endpoint information from the table entry to send the cluster information to the appropriate destination application

Click "Next Page" to continue.

Quiz