Mod_perl doesn't suck, and it certainly doesn't have a huge hit on the
CPU. (of course it all depends what you're doing, but for the most part
it's small)
Having used many high level web development environments, from C to
Java to TCL and perl, I find mod_perl at the top end of the scalability
From the start o' the thread:
But if I put in URL/directory and a forward slash/
eg. http://URL/directory/ then it shows the default.htm page. But I
know my
customers, and they will not put in the directory forward slash. How
do I
get around this issue?
This isn't really a mod_perl issue,
If you're simply looking for which link they clicked on to bring them to
this particular page/screen; it should be stored in $ENV{HTTP_REFERER}
Also:
my $prev_page = $r-header_in(Referer); #
http://www.someplace.com/withalinktohere.html
--A
Hello folks,
I am trying to find out where (which
That's usually pretty accurate, so I guess it really takes
that long on your system. Try Apache::Request! Or even one
of the lighter CGI modules like CGI_Lite.
in my case it means up to 4 connections per process, cause
in fact it
is not one module but 2 (input and output) and each
