Well, I see a difference between roles and groups and therefore I think it would actually be easier to separate them. Roles are very basic and only define the user's "level" of access. ie: the areas the user can access. Groups, however, can be more informative. They are not only an entity which has many objects, but depending on your application, they can be an entity other users interact with. For example, you may have feature where users can become "fans" or "friends" of the group "Yellow Team". "Yellow Team" may have it's own profile, avatar, etc. I don't see the same type of functionality being defined for roles. Thus, I think it's actually more clearer and simple to make the distinction between the two.
On Jun 11, 2:58 am, CMNAJS <[email protected]> wrote: > That makes things bit clear.. > > But Why we need roles and groups both? Isn't either of them is > enough.. and fulfill the requirement.. > As We can have users under groups in AROs and assign certain ACOs to a > group so that the usres of that group have access to those ACOs.. > > What you think?? > > And I am a bit worried about the management of all this... > Any idea for simplicity --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
