sure
to init before anything else.
Thanks for taking the time!
Gidon
I've had people run password guessing scripts and stuff.
I've handled it on a case by case basis, ie, limit the number
of wrong guesses.
There are a bunch of modules that can set limits as well which
can come in handy against very brutish sorts of misuses of your site,.
I used mod_throttle.c,
I must confess that I wrote a buggy but small script that makes perl
code unreadable. I promise. It basically removes comments, excess white space, and
changes all the
identifiers to weird names. It was during a
silly moment and I'm not proud. But, if you can get it to be any uglier,
we can
[EMAIL PROTECTED] wrote:
Hi,
Can folks please tell me what's the best way to pass large-ish amounts of
data between invocations of a CGI script.
If you have HUGE amounts of data which is way more than 3K,
then See CGI.pm and multipart/form-data.
For a big form, just make sure you use
Hello Everybody,
I believe it is true. We could have more more mod_perl programmers.
I think that the biggest problem/opportunity that mod_perl has in terms
of proliferation amongst programmers/users is that Hosts currently
do not provide mod_perl on cheap virtual server package.
I think a
If each transaction lasts a
couple of seconds, it this a Bad Thing?
I have always wondered about the point of using Mod_Perl vs Mod_CGI
where the program takes a couple of seconds to run completely.
To put it another way. Mod_Perl saves you some valuable time
which can make a difference
