Refactor caching system
Reported by Tim Gourley | September 1st, 2010 @ 09:50 PM | in 1.0 Stable Release
The caching system sucks as it stands. It was originally intended for filesystem-only caching, but Varnish support was hacked on to make Heroku happy. This should be pluggable and configurable instead.
Comments and changes to this ticket
-
Tim Gourley September 25th, 2010 @ 04:39 PM
- State changed from “new” to “open”
The system has been refactored, however padrino-cache is now out and available. That works with the filesystem, memcached, and redis, but not varnish.
It'd be nice to use padrino-cache since it is part of the core functionality of padrino and then perhaps move varnish header caching to a separate configuration.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Simple Ruby CMS showcasing the power of Padrino and MongoDB
Tim Gourley