Task #1952
closed
Feature #3744: Modularize NLSR
Decouple classes from Nlsr object for easier unit testing
Added by Vince Lehman over 9 years ago.
Updated about 5 years ago.
Description
Currently, multiple objects use an Nlsr object as a parameter in their constructor. This makes unit tests difficult since an Nlsr object must be initialized to test these components.
Classes:
HelloProtocol
Lsdb
NamePrefixTable
FileProcessor
Instead, the objects should take the information they require from Nlsr as parameters.
- Target version set to v0.5.0
- Assignee set to Nicholas Gordon
- Target version changed from v0.5.0 to Minor release v0.5.1
- Related to Feature #4288: Move sequence number file setting to the constructor added
- Related to deleted (Feature #4288: Move sequence number file setting to the constructor)
- Blocks Feature #4288: Move sequence number file setting to the constructor added
- Assignee deleted (
Nicholas Gordon)
- Status changed from New to Code review
- Assignee set to Ashlesh Gawande
- Target version changed from Minor release v0.5.1 to v0.5.0
- Start date deleted (
08/29/2014)
Current change, https://gerrit.named-data.net/c/NLSR/+/4398, does not pass individual components in the ctor if they are too many (example lsdb) but instead takes ConfParameter which has all parameters configured at the time of ctor initialization. It does resolve passing Nlsr to ConfFileProcessor and making things easier to initialize along with making classes independent of Nlsr object. Current change also does not enhance any tests, just make them compile and pass.
- Status changed from Code review to Closed
- % Done changed from 0 to 100
- Related to Task #4839: Move setInfoInterestFilter and setLsaInterestFilter to their respective classes added
Also available in: Atom
PDF
Updated by 
Updated by