I don't strongly disagree, but the table-driven approach is somewhat static. I
know that you can have alternatives in the table, and choose among them
dynamically, but the choices are still statically determined.
Just my opinion.
...Greg
Niket Agarwal (niketa@xxxxxxxxxxxxx) wrote:
For future versions of GEMS, it would be nice if the routing
function
could be modularized, so that it could be more easily replaced with
a
non-table-driven routing algorithm.
My feeling is that a table driven routing scheme provides more flexibility for changing the routing algorithm. One can easily change the table during configuration stage and use it as required during routing.
Cheers,
Niket
|