Oh, and one other thing ... Is it reasonable for me to expect that auth is the mechanism by which I would build a web2.0 social networking capability in web2py, or should I roll my own from scratch like I've done in the past, before using web2py?
In particular, I want to make a community where groups can be private or public and have a rich set of permissions. Such as: - User can/cannot join group without an invitation - Only members can see group in public listing - User can leave group - User can/cannot create new records associated with group - User can/cannot read records associated with group - User can/cannot update records associated with group - User can/cannot delete records associated with group ... etc. Obviously, the latter requirements are pure CRUD. However, I'm not sure about the stuff about joining, leaving, making visible/invisible, etc. I'm operating under the assumption that Auth will do a lot if not all this for me via permissions, etc. But are there any gotcha's in there waiting to pounce on me? Better yet, any good examples of a fully working system that does all this? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
