Changes between Version 47 and Version 48 of Old/NodeHandler/Multicast
- Timestamp:
- Apr 4, 2006, 3:18:43 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Old/NodeHandler/Multicast
v47 v48 93 93 '''R.6:''' 94 94 {{{ 95 The communication layer will keep track of whether all the NodeAgents have confirmed receipt 96 of a message sent from the NodeHandler. Till all ACKs confirming message receipt have been 97 received, it will keep resending the message. Once all confirmations have been received, it 98 will request the NodeHandler to send the next message. The server will not pipe the 99 individual ACKs and heartbeats to the NodeHandler. 95 The communication server will not pipe the heartbeats from the NodeAgents to the NodeHandler. 96 Instead, it will keep track of these messages on a per-node basis and on detecting a breakdown 97 in communication; it will send a RETRY message to the NodeAgent. The NodeAgent will consider 98 it to be a message from the NodeHandler. 100 99 }}} 101 100 102 101 '''R.7:''' 103 {{{104 The communication server will not pipe the heartbeats from the NodeAgents to the NodeHandler.105 Instead, it will keep track of these messages on a per-node basis and on detecting a breakdown106 in communication; it will pipe a message to the NodeHandler to issue a “HANDLER_RETRY” message.107 }}}108 109 '''R.8:'''110 102 {{{ 111 103 To send a message to the NodeAgent, the NodeHandler will pipe this message to the … … 116 108 }}} 117 109 118 '''R. 9:'''110 '''R.8:''' 119 111 {{{ 120 112 All issues relating to scaling impacts on the decision to use TCP will be thoroughly