Date: 08/25/01
- Next message: Julio Oliveira: "[phplib] Net_Curl how to take it...."
- Previous message: giancarlo pinerolo: "Re: [phplib] Re: [Phplib-users] preexisting perm integration"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
There is a new class proposed for handling the auth on objects.
It's in the CVS tree.
this is its intructory message:
http://www.geocrawler.com/lists/3/SourceForge/14160/0/6431668/
the classes in CVS are the acl_* ones
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/phplib/php-lib/php/auth/
I looked at it, and for me that should go into the User class, for the
reason I explain here
http://www.geocrawler.com/lists/3/SourceForge/14160/0/6479265/
with three advantages:
- you untouch the Auth class, so leave place for integrating past-future
packages/apps
- you have a live representation of that, which for me is more a 'state'
then a 'registered user credentials' (see my msg to phplib-core:
- you are not forced to redump every live [auth] modification to that
table (which is something you cannot pretend anyway to be done by
phplib), because youll' find the latest 'live' representation in the
USer class. This is what the author of PHPBugTraq found useful,
( http://www.geocrawler.com/lists/4/Web/195/0/6466737/ )
and recalls to that discussion with kk about 'what and why should you
keep fringes of data in the User array without dumping it to a
structured table'. The conclusion is that mostly depens on
stats/live_stats requirements...
- Gian
-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: Julio Oliveira: "[phplib] Net_Curl how to take it...."
- Previous message: giancarlo pinerolo: "Re: [phplib] Re: [Phplib-users] preexisting perm integration"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

