Feature #3274
closed
InMemoryStorage process MustBeFresh
Added by Junxiao Shi about 9 years ago.
Updated over 8 years ago.
Description
Extend InMemoryStorage to process MustBeFresh selector.
When a Data is added into the storage, the producer may specify "this Data may satisfy Interests with MustBeFresh selector for the next X duration; after that it may only satisfy Interests without MustBeFresh selector".
By default, this duration is infinity, which keeps the existing behavior that MustBeFresh is ignored.
This duration can be specified independent from FreshnessPeriod, which could be set to shorter so that the Data won't stay in ContentStore for too long.
- Assignee set to Yingdi Yu
- Target version set to v0.5
Yingdi agreed to work on the design during 20151013 conference call. See #2200 note-95.
Just a small question: why not just delete the data that is outdated? so that all data in the in-memory storage is assured to be "fresh".
it seems that with this approach, an interest with MustBeFresh will cause the InMemoryStorage to check each matched data one by one until it found the first data that is still within the specified period. Sound not very efficient to me...
Document of InMemoryStorage has been updated to reflect the change described in this issue.
why not just delete the data that is outdated?
Not all incoming Interests have MustBeFresh selector.
In StatusDataset use case, not serving stale Data can cause communication failure under certain timing conditions, as described in #2200 note-92 note-95.
This blocks a chain of issues, ultimately including autoregistration. Can a due date be set?
- Status changed from New to Code review
- % Done changed from 0 to 80
Document of InMemoryStorage has been updated to reflect the change described in this issue.
- Status changed from Code review to Closed
- % Done changed from 80 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by