Re: [Slashcode-development] ACLs for slashcode

[Chris N. <pu...@po...>]

At 18:02 +0100 2001.03.12, Alvaro del Castillo wrote:
>Hi!
>
>> Yeah, I was thinking about something very similar at one point, and think
>> this is a nice idea.  I wonder, though, if maybe users_param would be a
>> better user of this?  So instead of:
>>
>> >mysql> select op_insert_index from users_acl where uid=45;
>>
>> You would have:
>>
>>   select value from users_param where uid = 45 and name = 'op_insert_index';
>
>Yes, i have looked to this table and it is perfect for the use we are
>doing
>of users_acl. But the name and value fields must be bigger. A user can
>have
>lots of sections in wich it can do some operations. I don't know if
>when you designed the table you have in mind params so large.

Actually, users_param just uses a text field for "value" now.  So the only
issue would be picking a better limit for "name".


At 18:09 +0100 2001.03.12, Alvaro del Castillo wrote:
>Do you think that this model could replace the seclev model in
>the future? As I say in other email, I have found very easy to make
>co-live the to models in the transition.

I think so, yes, though there could be something i am not thinking of.
Currently we only use seclev for "is anonymous," "is regular user," "is
author," "is admin."  But this would be replaced by things like
"can_unlimited_moderate" etc. in the ACLs.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/