Hey everybody, thanks for you positive feedback and suggestions regarding my
login / session module for CGI::Application, which I am temporarily (for my
sanity) calling CGI::Application::Login & CGI::Application::Session, by no
means does this mean that I think my modules worthy of association by name,
just by function =).
Anyways, I've posted all the source files I have for the modules, including
example instance scripts and login screens. If you want to take a look and
try them out, please visit:
http://www.unobserved.org/cgiapp/
I am very open to any questions / comments / suggestions. If you think you
have an idea that can make this add-on for CGI::Application more powerful,
versatile, etc, or if your simply like the module and are thinking about
using it, but would like to see it better constructed and documented. Please
email me at [EMAIL PROTECTED]
Thanks for your time
===
steve comrie :: senior developer
www.shrinkingplanet.ca
----- Original Message -----
From: "Eric Berg" <[EMAIL PROTECTED]>
To: "Steve Comrie" <[EMAIL PROTECTED]>
Cc: "'cgiapp '" <[EMAIL PROTECTED]>
Sent: Thursday, November 15, 2001 3:06 PM
Subject: Re: [cgiapp] Is this useful? RFC
> I'd love to take a look at that, Steve. I'm about to write something
> like this for the project I'm working on right now. It's
> Perl/CGI/Oracle, and I was planning to use cookies for username and
> timeout.
>
> Thanks.
>
> EB/
>
> Steve Comrie: [Tuesday 13-November]:
>
> > 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]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
