Hi everybody, we are going to rebuild a big side in cake and like to have some opinion on the efficiency of the acl component.
Let's say we have a forum with 10.000 users and 100.000 posts. Everybody have to be logged in to read something. Like I understand the cake acl concept, you can grand everybody read access to the posts and the other user data with a few aco/aro/acl entries. But you need for every single user one aco, one aro and one acl entry to allow him to edit there own user data. I'm I right? And then you need the same amount of aro/aco/acl to allow a single user to edit there own posts. So you end up with a couple of 100.000 ' s entries (aco/aro/acl) that getting searched for every time you access an function. Is this a good solution for a basic application like the forum example? Right now we have an own access class that grants access to groups on every single function. So we ask on every function: does you group have access here? Additional we ask if the user_id is equal to the author_id than he has also edit rights. In this case we don't need additional db queries. Is the cake acl component meant to be used in such a example? Or is my cake acl setup wrong? Thank you for your opinion --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
