Changes between Version 5 and Version 6 of Old/NodeHandler/Broadcast
- Timestamp:
- Apr 10, 2006, 9:39:41 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Old/NodeHandler/Broadcast
v5 v6 42 42 '''R.3:''' 43 43 {{{ 44 The communication layer will use two separate approaches, one for sending messages and the 45 other for receiving messages. Messages being sent from the NodeHandler to the NodeAgent will 46 use broadcast. A single message will be broadcast by the NodeHandler and this message will be 47 received by all the NodeAgents. 44 The communication layer in the NodeHandler will use two separate approaches, one for sending messages and the other for receiving messages. Messages being sent from the NodeHandler to the 45 NodeAgent will use broadcast. A single message will be broadcast by the NodeHandler and this 46 message will be received by all the NodeAgents. 48 47 49 48 Messages being received from the NodeAgent will be use TCP. The NodeAgent communication layer … … 56 55 the NodeAgent. Since the communication layer will broadcast the message to all the nodes, the 57 56 NodeAgents will have the filters to deteremine whether a message is to be accepted / rejected. 58 57 Current NodeAgent code has such filters and these will be enhanced only if necessary. 59 58 60 59 After a message is sent, the communication server will wait for ACKs from the NodeAgent, which … … 86 85 The communication server will not pipe the heartbeats from the NodeAgents to the NodeHandler. 87 86 Instead, it will keep track of these messages on a per-node basis and on detecting a breakdown 88 87 in communication; it will send a RETRY message to the NodeAgent. The NodeAgent will consider 89 88 it to be a message from the NodeHandler. 90 89 }}} … … 103 102 == Software Design == 104 103 105 == Algorithm for NodeHandler Communication Server == 104 == Algorithm == 105 106 ''NodeHandler Communication Server'' 106 107 107 108 The NodeHandler on startup will open the required pipes and then fork the Communication Server
