The architecture of Authkit (and the examples/tutorial) seem to assume that users have access-control/permissions at the application-wide level.
The application I am developing requires access-control/permissions at the per resource level. i.e. each user has various permissions (read, write, edit, delete) on an arbitrary number of resources. Do any Authkit experts on this list have a strong view on how to use Authkit in this context? I'd rather not reinvent the wheel. Thanks, JB --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
