Actions
Bug #4218
closed
ChronoSync exclude interests should be mustbefresh
Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
08/03/2017
Due date:
% Done:
100%
Estimated time:
Description
For example: In a network we run ChronoSync-based application for a while. Then these applications quit but the network is still running NFD.
Now we restart ChronoSync-based application with the same sync prefix after some time. The application starts to get old data which has become
stale.
This is because exclude interest are not marked mustbefresh.
Updated by Ashlesh Gawande about 6 years ago
- Related to Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet added
Updated by Junxiao Shi about 6 years ago
MustBeFresh can’t save you in all cases. It’s still possible for a CS to have non-stale Data from an old session, if there are other consumers present that pulls Data into that CS. Instead, the consumer needs to express Interest with unique names in order to avoid old Data.
Updated by Ashlesh Gawande about 6 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Actions