You could use view predicates to add custom checks before views are called. If you use cached configuration values the overhead should be reduced to a minimum.
see predicates or custom_predicates http://docs.pylonsproject.org/projects/pyramid/en/latest/api/config.html#pyramid.config.Configurator.add_view 2013/1/15 Andreas Jung <[email protected]> > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Let's assume that we have a Pyramid site with several functional > sections. As part of maintenance operations you want to disable a parts > of the site e.g. by disallowing all views under a certain certain > route/path like /personal-data or so. My vision is having a central > place in my application where I can enable/disable the various parts > of the application with a click and this should have an immediate effect > without reconfiguration of app-servers, reverse proxies etc...any ideas > how to do this best with Pyramid? > -- Arndt Droullier / Nive cms cms.nive.co -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
