eZ publish rights system

Hi,

while talking to Derick at php|works he mentioned to me that ez 
Publish's rights framework works as follows:

ez Publish automatically picks up any modules that are dropped into the 
given folder and determines the available rights that come with that 
module from that. this means all rights are stored outside of the 
database. also one could confer that all rights from a given module are 
grouped in an area to stay within LiveUser lingo.

All other data, like group membership, rights assignments however are 
stored in the database.

Now I just wanted to mention this because we may want to support this 
kind. I think it should be necessary with the following steps:

1) No joins would be allowed on the rights or areas tables in the admin API
2) getRights() in the admin API would actually always have to grab its 
data via an observer, that would otherwise be used to read data from the 
cache (note we do not have this yet)
3) the client perm container need not use complex container or it needs 
to extend the complex container to modify the area admin and implied 
right reading

regards,
Lukas