I know this is a little late (email from last month)... but in regard to caching, isn't the major problem with implementing sessions in Radiant that the headers are cached as well? This seems to be over optimisation... Just cache the page text and let the headers be generated. Surely there isn't that large a hit in performance, and the advantage of using individual user sessions is great. Or make it an option at least, since most user ACL type systems require sessions...
> > Daniel Sheppard wrote: > > >>From looking at response_cache, there are only two features > that it > > > implements that the default rails action caching didn't (easily): > > > > > > - Expire Everything > > > - Expire After time > > > > It also caches the entire response (headers + body). > > Yeah, I left that off because I thought that the rails action cache > already did that - but regardless, the action_cache plugin adds that > behaviour. I'll push on ahead. > _______________________________________________ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
