Feature #137
Multi-connection bridge
| Status: | New | Start date: | 05/08/2017 | |
|---|---|---|---|---|
| Priority: | Normal (Code 4) | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
- Create updated version of bridge process to allow multiple incoming or outgoing connections.
- Needs to think about NodeID as we might just enum them virtually inside the cluster node, in this case short path responses shall not be used.
History
#1 Updated by Madars almost 4 years ago
Firstly we could start with allowing multiple tpbridge pairs between cluster nodes.
this would include some changes for:
- bridgedef_t should include the list of connected tpbridge processes. This needs a counter to for the number of connections established. If reached to 0, only then we consider other node disconnected.
- updates to other nodes may be sent via either connection
#2 Updated by Madars over 3 years ago
- multi-connection shall allow different node ids to come from single bridge process. Thus to cleanup service list / shared memory, needs to do some global service cross check, as service might be provided by other bridge process, if one is shutting down.
- also needs to think about smart shutdown. If we make tpbridge to shutdown, then firstly we shall unadvertrise all services to other node and only after a while perform process stop.