> It also seems to be a good idea not to put post request's
> response into
> a cache.
> A post supposed to change data, and the outcome of that should not be
> cached - I should not say OK if you just signed up as root...
class Page
def cache?
request.get?
end
end
Perhaps that should be the definition in core. Should fix that up.
As for parameters - a workaround that also gives you prettier urls would
be to have your page return itself from find_by_url and extract the
params from the url, so
/products?offset=1200&limit=10
becomes
/products/perpage/10/page/120
If you're doing things with query strings, I generally wouldn't allow
the page to be cached - there's too much variability -
offset=1200&limit=10 or limit=10&offset=1200?
You could also introduce a custom controller there, which might be a
better approach for trying to introduce such functionality into a CMS.
Dan.
_______________________________________________
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
