[horde] using horde perms to build apps

[Chuck Hagenbuch]

Quoting Alex Vorobiev <sasha at mathforum.org>:

> permissions is one of my major concerns as i am looking to implement a
> sufficiently flexible user/group/object/perm model.  having spent
> considerable time today looking at the Perms class, i am very confused about
> the horde permissions model and how it works.  i am getting lost in the
> words/variables perm, permission, perms, and so forth.  i am not quite
> following the relationship between the Perms class and the
> CategoryObject_Permission, and i am having trouble visualizing the data
> model and the logical relationships between arbitrary objects, their
> permissions (or permission objects), and so forth.  can someone possibly
> draw up a simple relationship diagram of some sort?  and perhaps shed some
> light on why permissions are implemented the way they are.

Hrm. I'm having trouble picking specific questions out of this. Basically:

- permissions are implemented on top of the Categories system, because it stores
arbitrary hierarchical data and thus makes it easy for us.

- CategoryObject_Permission is the class that maps to individual permissions
objects.

- Permissions can be applied to anything, but the checking has to be done by the
 permissioned object or application; the perms system just takes care of
answering permissions questions, not ensuring that they're asked.

That help at all?

-chuck

--
Charles Hagenbuch, <chuck at horde.org>
They're just looking at a wall of meat.