Re: RE: usage of PEAR::AUTH ?

the Auth class is a great idea, but it perhaps attempts to do many things and assumes too much. i think the functional features of Auth should be isolated. there should be an abstraction of storing persistent session data (allowing one to store session information either with PHP sessions or cookies, etc. with a flick of a switch). perhaps called Session. the (HTML) login screen functionality should be separated out. perhaps called Login the DB functionality should also be separated, and already has as Auth::Container /a On Thu, 3 Oct 2002, Guy Weatherburn wrote: > All, > > Must admit that despite having several years of PHP experience and over 25 > years of programming/scripting experience that I find the Auth module of > Pear to be an absolute pain!!!! For starters the ambiguity of the database > name and tables defaults are a no no!!! > the rest of it seems to be rocket science despite the fact that if you look > at the code it can not be. Can someone who really knows what is trying to be > done please write some tutorials along the lines of those available for the > DB stuff... This will clear up several problems for me and also for others > that are struggling.!!!??? > > Guy > The e-Guy Ltd (co.uk) > www.e-guy.co.uk > > PS Having decided (i.e. been forced by a potential client) would like to use > PEAR