begin quote from Kev on Apr 11, 2002: > We would introduce a new command for unregistered connections to server > ports--SECONDARY. We would also introduce a new server<->server command > with the token SC. SC would be prefixed by the introducing server and > would contain the same fields as a SERVER command--lag could lead to some > servers receiving the SECONDARY command before the SERVER command. We > need to discuss how to represent destruction of a secondary link--is a > SQUIT command enough, or must we introduce another command? We must also > discuss how the fall-back is to occur--if more than one SECONDARY link > has been established, how do we select which one to fall back to? > [snip]
A simple form would be: no server but the immediate neighbours would know about secondary links. Then, when the primary link is broken, instead of generating a SQUIT, generate a REROUTE message instead, telling what link was broken and where was it rerouted to. (This is off the top of my head, I'm sure there would be problems with such a setup). -- Alex Badea * Undernet Coder-Com contributer
