Description:
For users and hackers of Rack::Cache.
|
|
|
Meta-cache Performance
|
| |
Hi all,
I'm using rack-cache in front of an image generation server. My cached
files are large (images) so I currently write both caches to disk. I
read that I can increase performance by putting the meta cache onto
memcached. The problem is that I already have many gigabytes cached;
the meta cache is currently about 1GB and I expect it to grow quite a... more »
|
|
Storage instances
|
| |
I would like to use a Redis::Distributed instance for the metastore;
however, since rack-cache.metastore only supports URIs, I'm wondering
if this was an intentional design decision and if a concept like this
could be successfully merged into that design:
use Rack::Cache, :metastore =>['redis://redis1/0', 'redis://... more »
|
|
cache cleanup
|
| |
Hi all- So I am using a rack-cache Disk store in an image processing application I built <[link]>, which creates new cached resources based on URL query params. As there are a potentially infinite number of combinations and values of these params, the cache can grow without bound and leave lots of potential abandoned resources. I would like... more »
|
|
quastion about keys
|
| |
Hello everyone,
I loved rack-cache from the very first time that I used it, but now I
have a more complex requirement...
My app has a cookie with two important values: lang and country_code.
This values are similar to many people, but I need to cache
separately, because if I don't do it all the visitors see the site in... more »
|
|
Scrubbing cookies (and other headers)
|
| |
Hi all, We're migrating over to Rack::Cache, and it's awesome. However, one thing we ran into is that Rack::Cache is caching the Set-Cookie header from the original server response (since it just caches all cookies). That means, of course, that end-users are going to share cookies, which is less than desirable.... more »
|
|
Cache write and flush
|
| |
I want to know when every write and flush request comes in. I'm
trying to figure out the best way to hook the cache write and flush.
|
|
|