Am 05.01.2013 07:40, schrieb Michael Pedersen:
Hi there everybody. I've been letting these ideas sink in today a lot, and I feel like I'm on the verge of something that might manage to be a decent solution. I can't quite articulate it yet, though. It's taking ideas from filesystem ACLs, along with the ideas listed by both Kevin and Robert, and mashing them together into ... something.
Maybe we could add something like Pyramid's traversal mechanism, as an alternative to TG's object dispatch mechanism (which is actually a class dispatch mechanism). Or, if TG will ever be based on Pyramid, use that directly. In Pyramid, row level security can be established in a very natural way using traversal. I found that it often makes sense to have parts of the application use traversal (particularly for RESTish interfaces and arbitrarily nested documents like in a CMS) and other parts using static dispatch. Pyramid allows that. Maybe TG should also allow two different mechanisms, both somewhat higher level than Pyramid.
-- Christoph -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
