Quote:
If I say have a field let's say "rating" on a certain forum page that I would like to control access to, would the field be considered an "object" in your model?
|
Yes.
Quote:
I'm assuming the "forum page" would be created into the domains table.
The "rating" would be created in "objects".
|
Yes. I am not 100% sure of what you want to achieve but this makes sense. You could create a domain called 'forum page', and 'rating' could be an object belonging to that domain.
Quote:
|
How would I control access to that specific object?
|
Depending on how fine grained you want control your forum page you can either:
1) find out if a user is allowed to perform a certain action on the domain. (in this case it will be 'forum page')
2) or you could find out if a user is allowed to perform a certain action on the object itself (in this case rating.)
It really comes back to how you define your roles. The system is very flexible so it is up to you to think things through and build your roles accordingly.
Quote:
|
Or would it be that the "rating" field would be created as a "singular domain" in which case I would use that "singular domains" access priveleges?
|
Yes, and no. When ever you add an object to a domain, the system automatically creates an entry in the object table, which in essence is a 'singular domain'. It all comes down to how you query the database. You can either find out if a user can perform an action on a domain or an object. An object is always stronger than a domain (if ever there is a conflict.)
Having said this it really is up to you to define your roles appropriately. Give me more info on what you want to achieve and I can help you out more.