| 33 | | All communication will be handled in the communication layer which will be a separate process. ALC/LCT is a multi-threaded implementation and so we are not sure of the issues that may arise if it is made into a loadable library instead of a separate process. The present focus is on exploring reliable multicast and once this issue is resolved, the issues pertaining to converting this process into a loadable library will be addressed to. |
| | 33 | All communication will be handled in the communication layer which will be a separate process. |
| | 34 | ALC/LCT is a multi-threaded implementation and so we are not sure of the issues that may arise |
| | 35 | if it is made into a loadable library instead of a separate process. The present focus is on |
| | 36 | exploring reliable multicast and once this issue is resolved, the issues pertaining to |
| | 37 | converting this process into a loadable library will be addressed to. |
| 35 | | At this time, only changes to the communication layer in the NodeHandler is being considered. Similar changes to the communication layer in the NodeAgent will be considered later. At the moment, minor changes will be made to the current NodeAgent communication layer. The changes made will be limited to conforming to the new NodeHandler communication layer, e.g. existing UDP socket calls and socket processing code will be changed to that for TCP sockets. |
| | 39 | At this time, only changes to the communication layer in the NodeHandler is being considered. |
| | 40 | Similar changes to the communication layer in the NodeAgent will be considered later. At the |
| | 41 | moment, minor changes will be made to the current NodeAgent communication layer. The changes |
| | 42 | made will be limited to conforming to the new NodeHandler communication layer, e.g. existing |
| | 43 | UDP socket calls and socket processing code will be changed to that for TCP sockets. |
