Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Message-ID: <4EC25CF0.9050808@apache.org>
Date: Tue, 15 Nov 2011 13:37:04 +0100
From: Mladen Truk <mturk@apache.org>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:8.0) Gecko/20111103 Thunderbird/8.0
MIME-Version: 1.0
To: users@tomcat.apache.org
Subject: Re: AW: mod_jk Avoid loadbalancing
References: <739CCB2D4BF8FD48985D6E158AD327B81EBFB3C933@DC01.tecracerde.local>
 <4EC24FB3.7090407@pidster.com>
 <739CCB2D4BF8FD48985D6E158AD327B81EBFB3C980@DC01.tecracerde.local>
In-Reply-To: 
 <739CCB2D4BF8FD48985D6E158AD327B81EBFB3C980@DC01.tecracerde.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 11/15/2011 12:55 PM, Alexander Diedler wrote:
> Hello,
> Yes, it was an option to solve my problem. But what about the performance?
> My opinion was to forward only necessary requests to the Tomcat (jsp, java
> etc) and let the Apache HTTPD deliver the static content (CSS,JS,Images
> etc).
>

Use native connector and you won't have to worry about the static file performance.
It'll be few times faster compared to any proxy.
Unless you need httpd for something like php or special auth, use tomcat directly.

Regards
-- 
^TM

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org