feat(driver): new memory-meta
driver
#587
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #583
while experimenting I've noticed that adding metadata's to the default
memory
drive would introduce even a small amount of overhead (depending on the platform). So instead of modifying the original driver I decided to experiment and then build a new one, for those that are actually interested in it.It mimics the
*time
metadata from storages like fs, while supportingttl
(globally and per-key, to circumventlru-cache
limitation) and correctly dispose thesetTimeout
when the related key gets removed or storage disposed.I also fixed the
base
issue that is present in the defaultmemory
driver, although I plan to fix it as well in a separate PR