Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 51997 invoked by uid 500); 5 Sep 2001 04:54:34 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 51988 invoked from network); 5 Sep 2001 04:54:34 -0000 Date: Tue, 4 Sep 2001 21:54:14 -0700 From: David Rees To: tomcat-dev@jakarta.apache.org Subject: Re: Another funny thought this time about PHP Message-ID: <20010904215414.B4060@runt.ebetinc.com> Mail-Followup-To: David Rees , tomcat-dev@jakarta.apache.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from deacon_marcus@wwtech.pl on Wed, Sep 05, 2001 at 05:38:56AM +0200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, Sep 05, 2001 at 05:38:56AM +0200, Deacon Marcus wrote: > Hi, > Some of my co-workers are pushing for php support. While I'm strongly > opposing the idea (who needs php when jsp is available? imo that's plain > ridicilous), I thought, is it - theoretically - or would it be possible - to > set up Tomcat + Apache in a way where instead of standard model, all files > processed by Apache except those meant for Tomcat, reverse the roles - make > Apache "slave" of Tomcat, and use it only for, for example, php, while using > Tomcat for everything else including static content. You could easily do this by mapping *.php to a servlet, and have the servlet translate the requests to Apache. Not sure why you'd want to do this, isn't the performance hit with Apache in front of Tomcat negligible? -Dave