Task #2864
closed
A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntry
Added by Vince Lehman almost 9 years ago.
Updated over 6 years ago.
Description
Currently, NamePrefixTable::updateWithNewRoute() updates all the RoutingTableEntries for each NamePrefixTableEntry even if the RoutingTableEntry was not changed by the RoutingTable calculation.
Instead, NamePrefixTable::updateWithNewRoute() should only modify the NamePrefixTableEntry's RoutingTableEntries when they contain a RoutingTableEntry affected by the calculation.
- Blocked by Task #2862: Create flowchart for interaction between RoutingTable, NamePrefixTable, and FIB added
- Target version set to v0.3.0
- Target version changed from v0.3.0 to v0.3.1
- Blocked by Task #2863: NamePrefixTableEntries should store RoutingTableEntries using a pointer added
- Target version deleted (
v0.3.1)
- Target version set to v0.5.0
Because this is only an optimization and not of high urgency, this is going to v0.5.0. Additionally, because the currently-used topologies are not large, even full-refresh is not extremely costly.
- Blocks Task #4249: Make NamePrefixTable and RoutingTable communicate through signals added
- Status changed from New to Code review
- Assignee set to Nicholas Gordon
- Target version changed from v0.5.0 to v0.4.0
- Start date deleted (
06/09/2015)
- Has duplicate Task #4249: Make NamePrefixTable and RoutingTable communicate through signals added
- Has duplicate deleted (Task #4249: Make NamePrefixTable and RoutingTable communicate through signals)
Worth noting that the NPT no longer uses plain RoutingTableEntries, as issue #2863 has been implemented and closed. As such, this issue refers to the local copies of those entries that the NPT now keeps.
- Status changed from Code review to Closed
Also available in: Atom
PDF
Updated by 
Updated by