Changes between Version 43 and Version 44 of Old/NodeHandler/Multicast

Timestamp:

Apr 3, 2006, 8:58:23 PM (18 years ago)

Author:

sswami

Comment:

—

Old/NodeHandler/Multicast

@@ -66 +66 @@
 Since, the ACL/LCT implementation is not fully reliable in the sense that it doesn't guarantee
  reliable delivery, is the reason for putting a error correction mechanism on top.
+The NodeHandler will then wait for ACKs from the NodeAgent, which will be received through the 
+TCP socket. The communication server, after a pre-defined interval, will repeatedly send 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 
+command, will the NodeHandler proceed with sending the next command. 
+
+}}}
+
+'''R.5:'''
+{{{
+The communication layer will be a separate server that is running the reliable multicast 
+protocol. It will also handle all TCP socket related functions. The IPC mechanism between this 
+server and the NodeHandler will be implemented using pipes. When the NodeHandler wants to send
+a message to the NodeAgent, this message will be piped to the server which will then send the
+message using multicast. Again, when a message is received from the NodeAgent by this server, 
+it will pipe this message to the NodeHandler. 
+}}}
+
+'''R.6:'''
+{{{
+The communication layer will keep track of whether all the NodeAgents have confirmed receipt
+of a message sent from the NodeHandler. Till all ACKs confirming message receipt have been 
+received, it will keep resending the message. Once all confirmations have been received, it 
+will request the NodeHandler to send the next message.  The server will not pipe the 
+individual ACKs and heartbeats to the NodeHandler. 
+}}}
+
+'''R.7:'''
+{{{
+The communication server will not pipe the heartbeats from the NodeAgents to the NodeHandler. 
+Instead, it will keep track of these messages on a per-node basis and on detecting a breakdown
+ in communication; it will pipe a message to the NodeHandler to issue a “HANDLER_RETRY” message.
+}}}
+
+'''R.8:'''
+{{{
+To send a message to the NodeAgent, the NodeHandler will pipe this message to the 
+communication server. This message will contain information that will inform the server 
+whether to send the message to all the nodes or to a subset group of nodes.
+
+
+}}}
+
+'''R.9:'''
+{{{
+All issues relating to scaling impacts on the decision to use TCP will be thoroughly 
+investigated.
 }}}