You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 1, 2025. It is now read-only.
I ran into an issue of how to name the connection of a branch stack when the branch stack uses the same ip/port. An example of this would be, imagine you have a branching AFFIX AffixA, and the first branch consists of (CoordinationAffix)(AffixB) and second branch consists of (CoordinationAffix)(AffixC). Now if the application calls listenforconnection(myip, 12345), than one of the branches (lets say the one containing AffixB) should use port 12345 and the other branch will use a different port number. Now the CoordinationAffix from the root would already have advertised AffixA under the key 'myip:12345'. When the CoordinationAffix on the branch using port 12345 tries to advertise under the key 'myip:12345', there will be a collision.
One option would be to have both the branches use a different port number, but this would mean that the original port number that was provided by the application would not be used (unless we just open up a socket without using it).
The other option would be for the application to provide three unique names. One for the root, and one for each of the branches.
Here is how the example AFFIX composition looks like.