Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 26861 invoked from network); 2 Mar 2001 16:08:45 -0000 Received: from adsl-216-103-91-166.dsl.snfc21.pacbell.net (HELO simona.wyn.org) (root@216.103.91.166) by h31.sny.collab.net with SMTP; 2 Mar 2001 16:08:45 -0000 Received: from localhost (costin@localhost) by simona.wyn.org (8.11.0/8.11.0) with ESMTP id f238B0Z01113 for ; Sat, 3 Mar 2001 00:11:00 -0800 X-Authentication-Warning: simona.wyn.org: costin owned process doing -bs Date: Sat, 3 Mar 2001 00:11:00 -0800 (PST) From: cmanolache@yahoo.com X-Sender: costin@simona.wyn.org To: "'tomcat-dev@jakarta.apache.org'" Subject: Re: Proposed Server.xml Change (was RE: Bugzilla #512 is Bunk) In-Reply-To: <5B243E1DBC4D2648A46145FCA82682574FC9E1@SUS-CO1IT01> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > Right, but that is excruciating to configure and more excruciating to > maintain... We need to fix that :-) > Why not use two copies of Tomcat, each with their own mod_jk.conf-auto which > can be included in the appropriate VirtualHost section? Use 2 copies of tomcat as a workaround for stupid config mechanism ( I can say that, I wrote a large part of it :-) ? What if you have 1000 virtual hosts ? Don't get me wrong, sometimes it is good to have multiple instances of tomcat ( preferably on a farm of servers, or even on the same computer :-), for many valid reasons - but I wouldn't do it as a workaround for config. > Then we could map each ContextManager to one VirtualHost with one > auto-generated config file, and Include them from httpd.conf for each > VirtualHost accordingly? Except ContextManager represents a "Server" instance, not a virtual host. Mea culpa - a lot of people said that we need a VirtualHost object, but I (still) think it is not actually needed - Container can represent any "group" of URLs, including VirtualHost, Context, URLPattern, or any other mechansim. And Modules ( including config modules ) do have access to all this information and can generate anything they need. While this may be a bit confusing ( why don't we treat a virtual host in a special way ) it is also much more flexible and simpler to do, with simpler code. > Just some ideas... Thanks Steve. Please don't give up - maybe we can find a way to improve the config generator, or you may help with mod_webapp ( or ajp14 ) - i.e. extend the protocol to send Apache all the information about the hosts/web applications. Costin