On 28/08/2010 11:18, Domenico Briganti wrote:
Il giorno ven, 27/08/2010 alle 15.36 +0100, Pid ha scritto:
If you're using mod_jk you can enable the /jk-manager worker
(restricted
to known IPs only, of course) and take the cluster member out of
service
at the proxy level before disabling the
On 27/08/2010 23:30, michel wrote:
I have tried running PHP using Quercus, and I may have screwed it up but it
worked poorly, with some of the PHP code not being interpreted, instead
showing up on the wepage as text. I have also seen different PHP/Java bridge
implementation, but just
- Original Message -
From: Pid p...@pidster.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, August 28, 2010 7:45 AM
Subject: Re: PHP on Tomcat?
On 27/08/2010 23:30, michel wrote:
I have tried running PHP using Quercus, and I may have screwed it up but
it worked
michel wrote:
...
I can set up HTTPD, but I
am working of a rented Linux box with limited resources and HTTPD would
be resource heavy.
...
If you are already running Java stuff and Tomcat on that box anyway, then comparatively
speaking the additional resources usage by Apache httpd should
- Original Message -
From: André Warnier a...@ice-sa.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, August 28, 2010 5:02 PM
Subject: Re: PHP on Tomcat?
michel wrote:
...
I can set up HTTPD, but I
am working of a rented Linux box with limited resources and HTTPD
Hi Michel,
On 29 August 2010 00:31, michel compu...@videotron.ca wrote:
My idea about HTTP being a resource hog came from my ISP.
I don't get how your ISP comes to this conclusion. Compared with
Tomcat and Java, Apache Httpd is really lean, which is the main reason
why PHP hosting plans are so
unsubscr...@tomcat.apache.org
2010/8/29, Björn Wilmsmann bjo...@wilmsmann.de:
Hi Michel,
On 29 August 2010 00:31, michel compu...@videotron.ca wrote:
My idea about HTTP being a resource hog came from my ISP.
I don't get how your ISP comes to this conclusion. Compared with
Tomcat and Java,
Hello
I am starting async requests inside a asyncSupported=true servlet.
After that, sometimes an event occurs and I need to dispatch a small
message to each client. For this purpose I use a executor that will
send this message to each client in an obvious way:
for (final AsyncContext
