I'd like to build an app that has typical social networking capabilities. It seems as though auth_group and auth_membership have exactly the kind of functionality that one would like to apply to such things as making a user a member of a common interest group. In such a case, referring to the group by name makes more sense than role.
Should I customize auth_group to support additional fields, such as a group name? It seems somehow like this would be overloading the meaning of group, because I'd probably have an administrator role for managing the administration of my app, and then perhaps an administrator role for managing the people in my group list. Or is there a way for me to have my own group and membership relationships, within the app, that represent people belonging to common-interest groups, and have web2py do the administration of these groups and memberships using the web2py auth.has_membership types of functions? Or is it none of the above? -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
