Rafal,
>User is *not* a member of a Group.
>User is assigned a role *within* a Group.
>
>The code that Riley sent, would return the list of all Groups,
>in which at least one Role was assigned to the User in question.
That was the intent of that method. If a user has a role in group "X" then
they are a member of group "X" (by my reckoning and needs anyway). Even
though there isnt a direct relationship between the user table and group
table, if a user has a role assigned to them in group "X", then that allows
them to interact with group "X". In my case I have only one weak screen and
that is the login screen, after that if a user has not got a role in any
group, then they are not part of the application and are denied access.
Previously I had a BTA (Business Transation Area ) table which managed the
relationship between users, sites, services, etc but I found I was using BTA
as a psuedo Group. So dropped the BTA table as a key, and used TURBINE_GROUP
to link the sites, users, services etc. (Because of Torque the rewrite was
minimal) It is working really well and because of the convenience methods
for Group in Turbine, has often made it easier to do things.
This probably has you ripping your hair out, but for me anyway, the "user
has a role in a group therefore is a member of a group" is a satisfactory
description for the system I need to describe. The ACL system for Turbine is
proving very flexible for what I am doing, which is great! :)
Cameron Riley
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
