Re: Re: A session class (was Re: [PEAR-DEV] Namespace issues)

--- Martin Jansen <mail@martin-jansen.de> wrote: > In case of the authentication class, we also provide > some abstract > storage containers like databases, text files or > LDAP servers that > are easily accessible and have a clean-structured > API. Didn't know that. I'll read the script before I open my mouth next time. > The clean > structured API again applies to all PEAR code and > you can't really > say that your example has a (clean) API ;-). Well that's kind of the point I was trying to make. You don't always need a class file based API (clean or not) to accomplish what you need, quickly, and with few lines of code. I would extend that to say you don't (or maybe just me) don't need a big class file to "manage" sessions. Since this is about adding session management to auth.php and I don't use auth.php, I'll just mind my own business. David Norman - deekayen