Oliver brought up a good point in a different thread that I thought
I'd continue over here:
On 5/22/07, Oliver Baltzer <[EMAIL PROTECTED]> wrote:
> Radiant has built-in caching, one of Radiant's main features in fact.
> With this caching being enabled it does not need to query the database
> at all when a cached page is requested. This, however, is likely to
> conflict with your plans of fine grained authorization.
Yeah, that has kept me from doing page caching in Rails in the past.
One thought I'd had was to allow Radiant to do all the caching it
wants and in embed product specific classes or href rel attributes.
Then, post process the output (outside of Rails, probably using Apache
mod_xslt) with a user specific XSLT (which would possibly be generated
and cached by a GET request to a radiant extension that has a
controller with a respond_to.xsl {} block) to add things like the name
of the current user and remove information and turn off links to pages
they don't have access to.
This would also make it possible to make static html versions of
pieces of the site for burning to CD (which some of our customer's
demand).
Also, I'm guessing this is way more complicated than most
authorization schemes (I blame our sales dept... grr :) and it
probably has limited applicability outside of our operation. So if
you've read this far before hitting delete, thanks and I'd love
feedback!
-Andrew
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
