| | 122 | |
| | 123 | ==== (9/20) ==== |
| | 124 | A topology file/parser were added. The file is a .json list of upstream and peer controller units (nickname:host:port triplet). This list is used to instantiate client-side connections to the neighbors. |
| | 125 | |
| | 126 | The essential difference (as of not) between an upstream and peer unit are whether the client connection goes one way or both. Several ways to identify the origin of the message comes to mind: |
| | 127 | * keep the original lists of neighbors, and find relation by lookup per message |
| | 128 | * identify based on which message handler object receives message. The object: |
| | 129 | * is identified as down, up, or peer (relation) |
| | 130 | * manages outgoing connections to upstream or peer |
| | 131 | * raw classification: |
| | 132 | * if received on 6644 and no client connection to originator exists, it is from downstream |
| | 133 | * if received on 6644 and a client connection to originator exists, it is from a peer |
| | 134 | * if received on a high-number port and originator does not connect to 6644, it is from upstream |
