[Typo3-dev] backend ACLs

[Sven Wilhelm]

Hi Sebastian,

> so you would create an extra database table for storing the ACLs?
storing such data in a database table has the advantage of easy access.

When starting the ideas of acl there could be the question to implement 
a general way for using them. Due my use of OpenGroupware.org I know 
that computing acl could have high costs, so using standard sets of acl 
is a good way, and only set special ones if needed.

Dumped schema of the OpenGroupware.org ACL table:
--------------------------------------------------
              Table "public.object_acl"
     Column     |          Type          | Modifiers
---------------+------------------------+-----------
  object_acl_id | integer                | not null
  sort_key      | integer                | not null
  action        | character varying(10)  | not null
  object_id     | character varying(255) | not null
  auth_id       | character varying(255) |
  permissions   | character varying(50)  |
Indexes:
     "obj_acl_action_idx" btree ("action")
     "obj_acl_auth_id_idx" btree (auth_id)
     "obj_acl_object_id_idx" btree (object_id)
     "obj_acl_permissions_idx" btree (permissions)
     "obj_acl_sort_key_idx" btree (sort_key)

and a snippet of an "Select *"
-------------------------------
  object_acl_id | sort_key | action  | object_id | auth_id | permissions
---------------+----------+---------+-----------+---------+-------------
          26280 |        0 | allowed | 11540     | 20003   | r
          21440 |        0 | allowed | 20570     | 10110   | wr

Due the object-related model of the ogo-database the schema is not 
comparable to the typo3-db. but trying to see several types in typo3 
(pages, content, basic user data) as objects could make it a little bit 
comparable.

Greets Sven