Yes, I would like to use it on non-mod_perl environment too. I have written similar things before, but not as systematic as you described here.
On Tue, 13 Nov 2001, Steve Comrie wrote: > Yesterday, almost by accident I ended up writing a fairly neat and tidy > Login module using CGI::Application. > > It handles creating and placing a cookie and creates a session file (name = > value pair style) in a directory of your choice. > > It also let's you (encourages you to) sub-class it and overload the validate > function so you can decide how / and > whether or not a user gets validated. The overloaded validate function > should return a true or false and the Login module will either return an > error please try again, or set the cookie, create the session file and move > the user to the success page (or script) of your choice. > > Login page / error messages / cookie name / session file directory are all > defined by you in the login.cgi instance script. And a module like > MyProject::Login would use base 'CGI::Application::Login' and contain the > overloaded 'validate' function to decide how a user gets logged in. > > I was just wondering if anyone out there would find this useful. Maybe not > so much on systems running mod_perl, but on systems not running it. Anyways, > let me know and if there's any interest in it i'll pack it up a little > better, document it, and release it for everyone's enjoyment. > > Anyways, I hope I didn't ramble on too much and got my point across best as > I could. If you have any other questions please feel free to ask. > > === > steve comrie :: senior developer > www.shrinkingplanet.ca > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
