One of my companies built a framework based on a similar concept a while back on Pylons, and deployed around a dozen apps on it for ourselves and our clients.
It was really neat to get things off the ground, and quickly became a pain-in-the-ass as projects went through agile iterations -- everything started to depart drastically within the database , application, and caching/server structure. We ended up doing 10x more work to keep everything compatible - which ultimately defeated the entire purpose. If I were to do it again, I'd do this: - focus on making the is_logged_in validation ( setting , unsetting , persisting , integration with other frameworks like repoze , etc ) - just template out the login/logout logic into a scaffold or 'copy- paste' , and have it call the framework stuff that sets/unsets/checks the logged_in status. That might not be compatible with your goals, but if I had to do things all over again -- that's what I'd do. -- 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.
