Dont drop nodes on CR, and give busiest child as alt parent
Dropping "un-prefered" nodes
It is ok to drop a child (in order to make room for a incoming CR) only when that child has no children
Drop only on initial connect request
More statistics
Peers propose "best, lazy" child as alternative parent
Accept nodes without parents and drop my laziest child to it
Pick "best, lazy" child in source node
Logs..
Fixed PassNodeRequests.
Only accept nodes in your preferred stripe
Changes...
Forgot to include methods in last commit
Make sure to still forward packets while connecting to a new parent
Delay a reconnect
Differentiate betweens a CR in leaving or idle state
Removed unneeded stuff, new selection of preferred stripe
Spezialized canAccept() methods
Make sure we dont choose already disconnecting children in optimization
Weight for cost functions?!