Hi Sean,
My problem is that my sys admin person who needs to deploy this system
on a production box is concerned that Tomcat cannot be performant enough
to satisfy the high volume of requests on the server. He is convinced
that Tomcat is loaded every time anyone accesses the html, even if they
do not access the servlets themselves.
No, tomcat is already started. The tomcat process is running, waiting for
requests. Each requests is passed to an already spawned and waiting
thread. So handling a request is pretty fast. Tomcat behaves like a normal
webserver in this regard: started and waiting for requests.
Even the servlets inside Tomcat are started once at startup and then
are reused on every request in a separate thread.
HTML-serving is just another servlet in tomcat, that just reads a file and
passes it to the servlet output stream.
I assume your admin compares tomcat to CGI-programs. CGI-progams (mostly
written in Perl, thus often referred to as CGI-script) are started every
time a request goes to them; this indeed is not good for performance,
especially for scripts that need to start-up a huge interpreter that needs
to parse its script first.
One more point. These servlets must be in a secure environment. They
use a Thawte certificate for security. I thought Tomcat could be
configured to use a secure certificate fairly simply, but he says
otherwise.
Yes. Anyway I'd suggest to always use Apache as the frontend (handling
as well the SSL stuff) and then connect tomcat with AJP12/13 to the
apache.
ciao,
-hen
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
