| 66 | | Since, the ACL/LCT implementation is not fully reliable in the sense that it doesn't guarantee |
| 67 | | reliable delivery, is the reason for putting a error correction mechanism on top. |
| 68 | | The NodeHandler will then wait for ACKs from the NodeAgent, which will be received through the |
| 69 | | TCP socket. The communication server, after a pre-defined interval, will repeatedly send the |
| 70 | | command till it receives an ACK confirming receipt of a previously sent message from all the |
| 71 | | intended nodes. Only after all the NodeAgents have confirmed successful receipt of the |
| 72 | | command, will the NodeHandler proceed with sending the next command. |
| | 66 | After a message is sent, the communication server will wait for ACKs from the NodeAgent, which |
| | 67 | will be received through the TCP socket. All message-ACK correlation for each node will be |
| | 68 | done by the communication server. Also, it will, after a pre-defined interval, repeatedly send |
| | 69 | the command till it receives an ACK confirming receipt of a previously sent message from all the intended nodes. Only after all the NodeAgents have confirmed successful receipt of the |
| | 70 | command, will the communication server initmate the NodeHandler to proceed with sending the next command. |