I'm going to answer here too.. maybe it'll bring some life to the
group :)
As I understood, it's a matter of semantic and naming convention.
You choose how to divide/abstract the RBAC using roles, operations and
tasks.
However, if you have a set of auth. items which have something
incommon, I would recommend creating a task (without bizrules) and
assignning operations as its children (with bizrules). i.e : task =>
manage members | operations=> edit member, add member, etc..
Again, it depends on the abstraction from your prespective. But the
most important thing is to be consistent, so you won't get into too
much troubles with complex systems.
On Feb 19, 10:56 pm, Boaz Rymland <
boaz.ryml...@gmail.com> wrote:
> Hi all!
>
> First question for this to-be-extremely-busy-mailing-list - yey!
>
> Basically, I cannot fully understand Yii's RBAC definition of a "task".
> I've written a forum post that explains my need in a good manner, I hope.
> Right here<
http://www.yiiframework.com/forum/index.php/topic/28993-what-exactly-...>
> .