Feature #1996
closed
LocalControlHeader: caching
100%
Description
In LocalControlHeader, add a Caching feature.
Application MAY attach a Caching field on a Data packet to NFD, to give ContentStore an instruction about whether/how to cache the Data packet.
Initially, we only define one possible instruction:
- NoCache: ContentStore SHOULD NOT cache the Data packet.
Caching field MUST NOT be attached to a packet from NFD to application, or to a non-Data packet.
Updated by Junxiao Shi over 10 years ago
- Related to Task #1940: In Memory Storage added
Updated by Junxiao Shi about 10 years ago
The necessity of this feature is suggested by InMemoryStorage:
Since an application has already kept a copy of data packet, it should be able to inform the local daemon not to keep a copy in the content store.
Jiewen Tan, who's working on in-memory storage, has confirmed that the idea in Task Description satisfies the need from in-memory storage:
I just want to say I think the idea you provide is a good idea.
Updated by Junxiao Shi about 10 years ago
- Status changed from New to In Progress
Updated by Junxiao Shi about 10 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
LocalControlHeader rev25 and FaceMgmt rev43 are updated, please review.
Updated by Junxiao Shi about 10 years ago
- Status changed from Resolved to Closed
20141024 conference call approves this protocol design.
Before this can be implemented, we'll need fine-grained privilege control in NFD Management, because:
- Usage of CachingPolicy needs
faces/enable-local-controlcommand. - Most applications should be allowed to use CachingPolicy.
- Only few applications should be allowed to use other local control features.