From: Alvaro d. C. <ac...@ba...> - 2001-03-13 07:50:48
|
Chris Nandor wrote: > > Actually, users_param just uses a text field for "value" now. So the only > issue would be picking a better limit for "name". Ops, in 1.1.5 ... mysql> desc users_param; +----------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------+--------------+------+-----+---------+----------------+ | param_id | int(11) | | PRI | 0 | auto_increment | | uid | int(11) | | MUL | 1 | | | name | varchar(32) | | | | | | value | varchar(254) | | | | | +----------+--------------+------+-----+---------+----------------+ If the value is a text field it is perfect :-) I am going to try to follow your work in the CVS. Now I have installed slashcode 1.1.5 and I am working on it. Bye > > 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. Yes, the ACLs are very descriptive and very clear when other people have to work with them. We have a site that uses this scheme so we can use this experience and the code that we have developed. For example, a little web interface that let the user/admin edit ACLs. I will send patches to the list so you can see the code. Bye -- Alvaro > > -- > Chris Nandor pu...@po... http://pudge.net/ > Open Source Development Network pu...@os... http://osdn.com/ > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development -- =================================================== Alvaro del Castillo San Félix ac...@ba... Barrapunto.com |