Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 373
- Log:
Initial import of Radiant 0.9.1, which is now packaged as a gem. This is an
import of the tagged 0.9.1 source checked out from GitHub, which isn't quite
the same as the gem distribution - but it doesn't seem to be available in an
archived form and the installed gem already has modifications, so this is
the closest I can get.
- Author:
- rool
- Date:
- Mon Mar 21 13:40:05 +0000 2011
- Size:
- 1649 Bytes
| 1 | ## Backlog |
| 2 | |
| 3 | - Move breakers.rb configuration file into rack-contrib as a middleware |
| 4 | component. |
| 5 | - Sample apps: Rack, Rails, Sinatra, Merb, etc. |
| 6 | - Use Bacon instead of test/spec |
| 7 | - Work with both memcache and memcached gems (memcached hasn't built on MacOS |
| 8 | for some time now). |
| 9 | - Fast path pass processing. We do a lot more than necessary just to determine |
| 10 | that the response should be passed through untouched. |
| 11 | - Don't purge/remove cache entries when invalidating. The entries should be |
| 12 | marked as stale and be forced revalidated on the next request instead of |
| 13 | being removed entirely. |
| 14 | - Add missing Expires header if we have a max-age. |
| 15 | - Purge/invalidate everything |
| 16 | - Invalidate at the URI of the Location or Content-Location response header |
| 17 | on POST, PUT, or DELETE that results in a redirect. |
| 18 | - Maximum size of cached entity |
| 19 | - Last-Modified factor: requests that have a Last-Modified header but no Expires |
| 20 | header have a TTL assigned based on the last modified age of the response: |
| 21 | TTL = (Age * Factor), or, 1h = (10h * 0.1) |
| 22 | - Run under multiple-threads with an option to lock before making requests |
| 23 | to the backend. The idea is to be able to serve requests from cache in |
| 24 | separate threads. This should probably be implemented as a separate |
| 25 | middleware component. |
| 26 | - Consider implementing ESI (http://www.w3.org/TR/esi-lang). This should |
| 27 | probably be implemented as a separate middleware component. |
| 28 | - Sqlite3 (meta store) |
| 29 | - stale-while-revalidate |
| 30 | - Serve cached copies when down (see: stale-if-error) - e.g., database |
| 31 | connection drops and the cache takes over what it can. |
