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
Next idea.
If we drop Apache 2.0 support we need to have jk/jk2 jobs done somewhere :
What about Tomcat 5 & Coyote as a ajp13 dispatcher with advances and fine tuning rules, which could be updated in real time in via JMX ?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
