"Game_Ender" <[EMAIL PROTECTED]> writes: > Would it not be easier to have the information to be stored in the > database and create and some kind of "Users and Groups" tool for the > toolbox? The text based config file would work on some level, but with > the database you would keep the permissions with the data they are > protecting/controlling. So that any back up of the database will also > take the proper permissions with it.
I've been thinking about that as well... But the best thing with that is that you could define some kind of grouping for your classes and methods and protect them as a whole. Or you could simply classify all of your methods with a description (from the docstring? updated automatically?) on the database so that people have 100% granularity there. > More on the web based Identity manager. If it is created then that > tool can then be integrated into other Turbogears based projects that > need a users/groups/permissions system and want a web interface to it. > Things like photo galleries, forums, CMS packages all need a good web > based system for this. It would be valuable if each developer would > not have to reinvent this wheel. Maybe, as mentioned before, some callables to get those information are enough. Then you'd just have to apply your decorators with such callables. No more work than you do today and your callables code is 100% reusable (and could become a product by itself, a kind of "plugin"). -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
