Hi Ker,
It'll be the web server which is handling the requests obviously - probably
Apache. If your running Perl CGI without mod perl installed in Apache then
each request for the CGI will, I believe, cause another external process to
be created invoking the system Perl compiler, the compiled results are then
executed and the resutls returned  the webserver for returning to the
client - the compiled script is then effectively 'lost' - the next request
to the CGI starts the cycle again. mod-perl effectively stored the compiled
perl script to minimise the recompilation process and uses a Perl compiler
embedded into Apache itself for maximum speed. mod-perl does have its own
gotchas when dealing with multiple requests which are well documented.

CGI Carp will give you plenty of stuff to look at in the web browser rather
than the dreaded 500 error.

And I bet there is module for Perl to write to the Apache log - search on
search.cpan.org and I'm sure you'll find one.

regards

Joel

-----Original Message-----
From: Kerr Wall [mailto:[EMAIL PROTECTED]]
Sent: 16 July 2002 17:54
To: [EMAIL PROTECTED]
Subject: Couple of newbie questions


Hi All,

I am currently switching to Perl/CGI from the Java servlet world.  I'm
wishing I would have made this switch a long time ago and I have a
couple of questions:

How does perl handle multiple requests.  For example, if 10 users are
logged into your system and they are all trying to use the same script,
how does perl deal with this situation?

What is the best way to test and debug?  I am use to printing to the
console with Java and I'm not sure how I do this with perl.  Does apache
have a log file that I can write to and how to I keep track of when I
want to print the response or print to stdout/log file?

Thanks,

Kerr Wall


--
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]

Reply via email to