> > Oh no, the framework doesn't depend on using a session > > at all. Just this particular auth module depends on > > plugging in the session beforehand. > > So I have to have a persistant backstoring session in > order to use the auth module?
Well, now, but as you recommended, maybe not necessary. > I'd think 'implementation subclass must implement a method > that returns validity of username' would be more flexible > and concise. You could use apache environment variables > and other request state information to pass extra data to > that function based on what <file> or <location> or > <directory> its in, as a forinstance. Well, it would get $r. Yes, I thought it would be a good idea to rework it so getting the username is its own method, that way you could subclass and get it from LDAP or whatever. Actually in that case, it's not clear that even a DBI handle is necessary for the top-level implementation, although if you use the connector handler to get one in your subclass you could do joins or whatever you need to do. Then I can also drop the directives for the table name and field names. Thanks for the advice! There may be something wrong with your mail program, or with alpine's way of reading your mail. It's hard to sort out where I wrote and where you wrote because everything has only one level of '> ' quotes. Mark
