tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <>
Subject Re: TC evolment
Date Sat, 03 Apr 2004 07:14:02 GMT
Mladen Turk wrote:
>>-----Original Message-----
>>From: jean-frederic clere 
>>What do you want to do?
>>- Call native methods in TC to get PHP running.
>>- Write a servlet engine that understands PHP. (Well the 
>>problem would be the libraries).
> If a majority of my web content is a dynamic one, delivered through JSP,
> PHP, or what ever, why would I need a dummy web server as an intermediate?

> That's my thoughts. True, I'm thinking of having native connection to PHP,
> but that's irrelevant compared to the concept itself.
> Nowadays we are having connectors (to the so called mighty webservers) to
> the TC, but I'd like to rotate that a bit. Static content is becoming less
> and less significant than before, and I cannot imagine a ISP provider that
> doesn't offer some dynamic content 'connector'.
> I think that we need to change the thinking perspective from TC being a
> 'helper' to TC being a 'workhorse'.

The webserver is not only for static content. If you use Apache just 
because it serves the static content faster than tomcat - you are using 
it for the wrong reason.

A lot of people use Apache because they feel it's more stable and secure.
Other use it because of the hundreds of modules - like mod_php, 
mod_perl, etc. Yes, you could make mod_php work with tomcat - or you 
could even rewrite the entire php in java. And nobody can stop you from 
doing this if you have the time and itch.
But if you just want to use PHP instead of JSP - you may be better just 
  doing it with the existing stable solution, which is Apache.

The raw page speed is not everything. There is also the memory use, CPU 
load, startup time, stability, etc.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message