Task #4249
closed
Make NamePrefixTable and RoutingTable communicate through signals
Added by Nicholas Gordon over 7 years ago.
Updated about 7 years ago.
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.
- Blocked by Task #2864: A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntry added
- Status changed from New to Code review
- Status changed from Code review to In Progress
- Is duplicate of Task #2864: A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntry added
- Status changed from In Progress to Code review
- Is duplicate of deleted (Task #2864: A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntry)
- Status changed from Code review to Closed
Are you going to change shared_ptr to unique_ptr?
Also available in: Atom
PDF
Updated by 
Updated by