I guess I had thought that this new model fit nicely within
abstraction barriers -- ask the component to "do whatever you need to
do to warmup your routes". The knowledge how to do that is already
down in that component; is there really a reason/need to export it
higher?
On Jun 19, 200
I would argue that this behavior is in fact consistent - the returned state
is that all required connections have been opened and is independent of the
selected routed module. How that is done is irrelevant to the caller.
Each routed module knows precisely what connections are used for its
operati
Ralph,
I don't necessarily agree with this statement. There is a generic
method to do the correct wireup, and this method works independent of
the selected routed algorithms.
One can use the routed to ask for the next hop for each of the
destinations, make a unique list out of these first
