On 16-Apr-2002 Kee Hinckley wrote: > At 2:23 PM -0700 4/16/02, Wim Kerkhoff wrote: > > You should always be doing validation on the back-end as well, if > only to defend against malcious users.
That goes without saying... protection against both malicious and brain dead users. >>I found Embperl pretty easy to learn... the problem is not having lots of >>sophisticated source code to learn from. > > Yes, we definitely need to start contributing things. It would help > if someone would come up for a standard install mechanism for a > package which combines perl modules, html code, images, embperl html > code and embperl modules. We don't even at this point have a > standard for where most of those things go--let alone an installer. Where does one start? Are there any installers for other CGI projects that can be imitated? I started writing an installer for acmemail [1] in the style of CPAN::FirstTime, but haven't completed it. Makefile.PL needs to prompt for the various locations, session settings, database settings, etc. Do you force the person installing it to read the documentation and figure out what to add into httpd.conf and startup.pl? Do you store settings only in httpd.conf via PerlSetVar? Or use a INI/XML like file that can be loaded? Or do you write out a MyApp::Config.pm, which can be require()'d later and rewritten? I never really completed the acmemail installer as I didn't like where it was going. Now I can't find the code either... I should have committed it into CVS as a branch, but didn't. 1. http://sf.net/projects/acmemail Regards, Wim Kerkhoff -|- www.nyetwork.org -|- [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
