Actions
Task #3815
closed
Handle NACKs in Sync module.
Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
10/17/2016
Due date:
% Done:
0%
Estimated time:
Description
Currently Sync does not do anything to handle NACKs. Since NLSR is using a forked version of Sync, we are not in a position to refactor it heavily to do so. However, we should refactor Sync to process them minimally by logging the NACK and its context, i.e. the function name that was executing, the logical "task" we were in, etc., so that we can understand the kind of NACK behavior that Sync is producing.
Updated by Nicholas Gordon about 8 years ago
- Related to Task #3799: Write specification for NLSR NACK behavior. added
Updated by Nicholas Gordon over 7 years ago
- Status changed from New to Rejected
Rejected since NLSR no longer maintains a forked version of ChronoSync.
For the corresponding issues in the ChronoSync tracker, see:
https://redmine.named-data.net/issues/3716 and
https://redmine.named-data.net/issues/3715
Actions