Update Redis::Rack::Cache to v2.2.0
#223
Merged
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
This new version requires `Rack::Cache` v1.10 and enables over-the-wire gzip compression to the Redis server. This feature is useful for extremely high traffic sites, but should be used with caution since it will increase the CPU/RAM load on your application server. You should use this if the trade-off between RAM increase and bandwidth decrease makes sense. WORKAREA-94
tubbo
force-pushed
the
WORKAREA-94-update-redis-rack-cache
branch
from
9acfcb0
to
ef3d5b7
Compare
bencrouse
approved these changes
Nov 11, 2019
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.
This new version requires
Rack::Cachev1.10 and enables over-the-wiregzip compression to the Redis server. This feature is useful for
extremely high traffic sites, but should be used with caution since it
will increase the CPU/RAM load on your application server. You should
use this if the trade-off between RAM increase and bandwidth decrease
makes sense.
WORKAREA-94