Project

General

Profile

Actions

Task #4249

closed

Make NamePrefixTable and RoutingTable communicate through signals

Added by Nicholas Gordon about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Target version:
-
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.


Related issues 1 (0 open1 closed)

Blocked by NLSR - Task #2864: A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntryClosedNicholas Gordon

Actions
Actions #1

Updated by Nicholas Gordon about 7 years ago

  • Blocked by Task #2864: A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntry added
Actions #2

Updated by Nicholas Gordon about 7 years ago

  • Status changed from New to Code review
Actions #3

Updated by Nicholas Gordon about 7 years ago

  • Status changed from Code review to In Progress
Actions #4

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
Actions #5

Updated by Nicholas Gordon about 7 years ago

  • Status changed from In Progress to Code review
Actions #6

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)
Actions #7

Updated by Nicholas Gordon about 7 years ago

  • Status changed from Code review to Closed
Actions #8

Updated by Ashlesh Gawande about 7 years ago

Are you going to change shared_ptr to unique_ptr?

Actions

Also available in: Atom PDF