Changes between Version 47 and Version 48 of Old/NodeHandler/Multicast


Ignore:
Timestamp:
Apr 4, 2006, 3:18:43 PM (15 years ago)
Author:
sswami
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Old/NodeHandler/Multicast

    v47 v48  
    9393'''R.6:'''
    9494{{{
    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.
     95The communication server will not pipe the heartbeats from the NodeAgents to the NodeHandler.
     96Instead, 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
     98it to be a message from the NodeHandler.
    10099}}}
    101100
    102101'''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 breakdown
    106  in communication; it will pipe a message to the NodeHandler to issue a “HANDLER_RETRY” message.
    107 }}}
    108 
    109 '''R.8:'''
    110102{{{
    111103To send a message to the NodeAgent, the NodeHandler will pipe this message to the
     
    116108}}}
    117109
    118 '''R.9:'''
     110'''R.8:'''
    119111{{{
    120112All issues relating to scaling impacts on the decision to use TCP will be thoroughly