Re: Auth

Hello Chuck, On Mon, Jan 08, 2001 at 10:00 -0500, Chuck Hagenbuch wrote: > > Quoting Mikhail Zabaluev <mookid@sigent.ru>: > > > Well, I did some scratching on that. In my vision, it could be a bunch of > > classes with generic interface(s). Different classes would cover DB-based > > authentication, tokens supplied via standard HTTP auth, storage of auth > > data in session etc. We could team up on the design of this thing. > > It seems there are two pieces needed, something like Auth_Store and Auth_Token. > Both of these should be abstract classes, and any Auth_Store should be able to > work with any Auth_Token (although I can think of a few scenarios where this > wouldn't be the case, but I don't think it breaks the design). How would it handle extended schemes that employ, for example, user groups or other auth-related properties? Which class should encapsulate verification? -- Stay tuned, MhZ mailto:mookid@sigent.ru ----------- Death, when unnecessary, is a tragic thing. -- Flint, "Requiem for Methuselah", stardate 5843.7