Exposes LockingCache configuration to adjust ttl and expire policy #97
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LockingCache now accepts deleteOnHit option to delete objects when they are requested even if they were set with a ttl/timeout > 0. MapnikSource now accepts configuring ttl and timeout/ttl for the internal locking cache so it's possible to combine it with metatiling in a more efficient manner. Now it's possible to use metatile, use a ttl>0 and remove on hit, so cached objects from metatile will be removed after ttl but objects already requested are removed as they get a hit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
LockingCache now accepts deleteOnHit option to delete objects when
they are requested even if they were set with a ttl/timeout > 0.
MapnikSource now accepts configuring ttl and timeout/ttl for the
internal locking cache so it's possible to combine it with
metatiling in a more efficient manner.
Now it's possible to use metatile, use a ttl>0 and remove on hit, so
cached objects from metatile will be removed after ttl but objects
already requested are removed as they get a hit.