Actions
Feature #3917
open
Implement InMemoryStorageTimeout
Status:
New
Priority:
Normal
Assignee:
-
Category:
Utils
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Tags:
Description
This flavor of InMemoryStorage should remove items based on the specified expiration time associated with the inserted item. The storage can also have persistent or LRU/LFU/Random replacement semantics.
Updated by Davide Pesavento over 7 years ago
- Tracker changed from Task to Feature
- Subject changed from Implement InMemoryStorateTimeout to Implement InMemoryStorageTimeout
Updated by Eric Newberry almost 4 years ago
- Status changed from New to In Progress
- Assignee set to Vedaant Rajoo
Updated by Vedaant Rajoo almost 4 years ago
Need more clarification
Does the timeout need to a different option or should it be based on the FreshnessPeriod?
Because this would mean that whenever a packet is notFresh, it should be erased from the inMemoryStorage.
Updated by Davide Pesavento almost 4 years ago
It should be simple to support both. Have an optional<time::milliseconds> as a constructor parameter, with a default of nullopt. If this parameter is specified, use that as timeout, otherwise use the packet's FreshnessPeriod as timeout.
Updated by Davide Pesavento over 1 year ago
- Status changed from In Progress to New
- Assignee deleted (
Vedaant Rajoo) - % Done changed from 20 to 0
Actions