Henri Gomez wrote:

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'.


Interesting idea Mladen.

+0

<wistful-smile>
And to think it was only a couple of years ago that I got thorougly chastised (by more than a few people participating in this thread :-) for suggesting that Tomcat standalone might actually be a viable production solution for some applications.
</wistful-smile>


The recent improvements in the perfornance of Tomcat standalone (with refactorings like the Coyote connector, plus other optimizations in the Catalina core) have definitely widened the scope of applications where Tomcat standalone is "good enough" ... but it always has been for any departmental app with a limited user population (which is a many-orders-of-magnitude number of real live apps). I'm glad to see that the "Tomcat isn't worthy of standalone status, it needs to be hidden behind a *real* web server" crowd are finally coming to understand that there is a substantial number of use cases where Tomcat standalone is a perfectly reasonable solution.

Or, if you'd prefer it in a sound bite ... "fast enough is fast enough". If Tomcat standalone meets your performance requirements, you have my blessing if you choose to avoid the pain of learning how to configure it to integrate with Apache's HTTPD server :-).

Craig McClanahan


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to