On 1/2/07, Langdon Stevenson <[EMAIL PROTECTED]> wrote:
This implies heavily that limiting the number of Acos is the key. Can you give an example of how a user may accumulate large numbers of Acos?
Yes, if you see to my previous example - getting in findAll* which pictures/albums/categories a user is allowed to see (depending which group she belongs to) you will soon have a large number of ACOs
I think that you are probably right. The question then becomes: is this a problem? If so, why is it a problem?
The problem for me is what would be a DRY way to do this. I very easily can do it the usual way by adding criteria to findAll or even some funky bindModel stuff, but this way there is access restriction code in almost every controller / model. This for a large project soon gets to be P2C2E (Process too Complicated to Explain) unless explained in great details at every step. May be it needs inversion of approach to solve it.... Cheers Tarique -- ============================================================= PHP Applications for E-Biz: http://www.sanisoft.com Cheesecake-Photoblog: http://cheesecake-photoblog.org ============================================================= --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
