Re: Auth

Quoting Paul Meagher <paul@datavore.com>: > You may want to take a look at http://phplib-4.myip.org/ for > some recent > work that has already been done on this. I am just testing it out now. > Also, phplib's Session class and User class are also undergoing active > development if you check out the cvs tree at phplib.netuse.de (or the > archived newsgroup). Is there anything different here (in the Auth class) from standard phplib? I was a bit confused as to what exactly that page was... > The main difference between PHPLIB's approach and what you are suggesting > seems to be that PHPLIB's Auth depends on more generic classes to supply > the container and session management support. In other words, the Storage and > Token support could be used in, say, a Cart class as well. I don't know if things have changed recently, but the last time I looked at it, phplib's CT (container) classes were no good for storing anything but phplib sessions... > My worry in developing a PEAR version of this stuff is that I have no > samples to work from showing me how the DB class works (which is the most > common way that authentication information is stored). Also, I am not sure > how stable the API for the DB classes are - I know there is still some > uncertainty about how error reporting should work. How stable is the DB API > and are there any samples showing how it works? There is code in the Horde repository that uses the DB classes. As for stability, the API should be fairly stable - the error reporting changes most likely won't change how you interact with the class. -chuck -- Charles Hagenbuch, <chuck@horde.org> "If you can't stand the heat, get out of the chicken!" - Baby Blues