Actions
Task #4249
closed
Make NamePrefixTable and RoutingTable communicate through signals
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Currently, there is a direct function call chain from the calculation of the RoutingTable to the population of the NamePrefixTable. This means there is no way to conveniently test or change these mechanisms without significant rework. It would be better if the RoutingTable had no knowledge of who was listening for routing information updates.
Updated by Nicholas Gordon over 7 years ago
- Blocked by Task #2864: A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntry added
Updated by Nicholas Gordon over 7 years ago
- Status changed from New to Code review
Updated by Nicholas Gordon over 7 years ago
- Status changed from Code review to In Progress
Updated by Nicholas Gordon about 7 years ago
- Is duplicate of Task #2864: A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntry added
Updated by Nicholas Gordon about 7 years ago
- Status changed from In Progress to Code review
Updated by Nicholas Gordon about 7 years ago
- Is duplicate of deleted (Task #2864: A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntry)
Updated by Nicholas Gordon about 7 years ago
- Status changed from Code review to Closed
Updated by Ashlesh Gawande about 7 years ago
Are you going to change shared_ptr to unique_ptr?
Actions