"GB" == Gunther Birznieks [EMAIL PROTECTED] writes:
GB Does the size of CGI.pm really matter with mod_perl so much? If the module
GB is pre-loaded prior to forking, wouldn't the memory for this module tend
GB to be shared anyway? Or is there still a gradual hit to real memory as
Yes it is
"DM" == Doug MacEachern [EMAIL PROTECTED] writes:
DM geez. i don't recall "Apache::Registry vs. pure PerlHandler" or
DM "Apache::Request vs. CGI.pm" ever being so harsh.
Personally, I do all my scripting in Apache::Registry. Why? Because
it is easy, and I don't always have the ability to
On Fri, 31 Mar 2000, Vivek Khera wrote:
My question to all of you who use handlers directly, how do you manage
all your handler mappings? I've seen it done where you add a
Location mapping for each handler you use, which corresponds to each
"program" you need. This, in my experience, tends
geez. i don't recall "Apache::Registry vs. pure PerlHandler" or
"Apache::Request vs. CGI.pm" ever being so harsh.
but they have been compared, for good reason.
Apache::Registry maps a request to a file and generates a subroutine to
run the code contained in that file. if you use a
CGI.pm is a great piece of code, but its very monolithic. Lincoln/Doug's
libapreq module is probably much faster (I have never run benchmarks) than
CGI.pm, so it makes sense for those who like the Q-param type interface
(I do) for working with CGI environment variables, but don't need all the
