Task #2400
closed
Determine the necessary changes to use current Chronosync as dependency
Added by Vince Lehman over 9 years ago.
Updated almost 7 years ago.
Description
Currently, NLSR uses its own forked and modified version of Chronosync.
Updates and bug fixes to Chronosync are not being incorporated or tracked.
Ideally, NLSR should use Chronosync directly and not maintain its own version.
This task should determine the effort and changes necessary to stop using a forked version of Chronosync and instead use the main repo.
- Target version set to v0.5.0
- Assignee deleted (
Vince Lehman)
- Blocks Task #1523: Use separate name prefix and sequence number for each LSA type in ChronoSync added
- Related to Task #2375: Jenkins fails build during OpenSSL linking added
Will need to remove openssl dependency after this is completed.
NLSR maintains its own sequence numbers (https://redmine.named-data.net/projects/nlsr/wiki/Handles_synchronization_logic_of_NLSR_LSDB_updates).
Chronosync does not to allow applications to set sequence numbers and maintains its own sequence numbers.
Making Chronosync a dependency is very simple and straightforward if a small API change can be made in Chronosync to allow setting of sequence numbers in publishData methods.
Apart from benefits mentioned in description we can rid NLSR of two dependencies: openssl and protobuf.
- Blocked by Bug #3990: ERROR: Interest size exceeds maximum limit on exclude interest for large topologies added
- Blocked by Feature #4032: Allow applications to set sequence number added
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to Ashlesh Gawande
- Target version changed from v0.5.0 to v0.4.0
- % Done changed from 0 to 80
- Status changed from In Progress to Feedback
- % Done changed from 80 to 100
- Status changed from Feedback to Closed
- Related to Bug #4513: Need to use a fixed session name for ChronoSync sockets added
Also available in: Atom
PDF
Updated by 
Updated by