On May 31, 2006, at 7:49 AM, Charlie Bowman wrote:
Sorry, for the slow reply. I'm only registered for this list at my
work address and there's no way I'm going to set my home computer
to check that email!
You're right I could definitely use a redirect statement to make
caching work, but it seems like a hackish maneuver. As soon as
this rewrite goes into the core, I'll work on a plugin to retrieve
the long_url_for.
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.
- 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.
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.
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
