Yes, this is how I deleted my entire public directory during testing. This is also why I could retrieve the long url by adding the extra route.Really what is required is to produce all the urls for a given resource. The two main problems with page caching are: - A cached page may be located at several paths. The big issue here is that only the first route matched will be swept on changes.
I think most people who rely heavily on page caching have started putting all query parameters into the url. I'm of the group that advocates putting all query parameters into the url if possible. Although, I agree that if page caching worked with query parameters, there would be a lot of happy users out there!- Query parameters mess up caching; if you create a cache page with query parameters, then the same request without query parameters will hit the cache, even though there is a strong probability that it shouldn't.
I think I fall into the "common" user category, nothing too basic and nothing too complicated yet, and this would really help me with page expiration. This would also eliminate the need for me to have a long_url_for method.Adding a mechanism to generate all valid paths for a param set can help us fix sweepers so that they erase all the cached versions, as they probably should.
|
Charlie Bowman http://www.recentrambles.com |
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
