Return-Path: 
 <dev-return-52566-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 18454 invoked from network); 5 Dec 2003 23:18:47 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 5 Dec 2003 23:18:47 -0000
Received: (qmail 34639 invoked by uid 500); 5 Dec 2003 23:17:43 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 34568 invoked by uid 500); 5 Dec 2003 23:17:43 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 34424 invoked from network); 5 Dec 2003 23:17:42 -0000
Received: from unknown (HELO main.gmane.org) (80.91.224.249)
  by daedalus.apache.org with SMTP; 5 Dec 2003 23:17:42 -0000
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 1ASPCm-0004zh-00
	for <dev@cocoon.apache.org>; Sat, 06 Dec 2003 00:17:48 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: dev@cocoon.apache.org
Received: from sea.gmane.org ([80.91.224.252])
	by main.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 1ASPCl-0004zX-00
	for <gmane-text-xml-cocoon-devel@m.gmane.org>;
 Sat, 06 Dec 2003 00:17:47 +0100
Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian))
	id 1ASPCk-0005G4-00
	for <gmane-text-xml-cocoon-devel@m.gmane.org>;
 Sat, 06 Dec 2003 00:17:46 +0100
From: Sylvain Wallez <sylvain@apache.org>
Subject: Re: Load Balancing web applications with mod_proxy...
Date: Sat, 06 Dec 2003 00:17:47 +0100
Lines: 46
Message-ID: <bqr3mq$jhg$1@sea.gmane.org>
References: <BBF43344.3C1B0%pier@betaversion.org> <3FCF376D.50603@upaya.co.uk>
 <bqq8r2$m3l$1@sea.gmane.org> <3FD0AFF2.8040406@upaya.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20031007
X-Accept-Language: fr, en, en-us
In-Reply-To: <3FD0AFF2.8040406@upaya.co.uk>
Sender: news <news@sea.gmane.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Upayavira wrote:

> Sylvain Wallez wrote:
>
>> Upayavira wrote:
>>
>> <snip/>
>>
>>> If relevant, I've started extending the MountTableMatcher to include 
>>> the code from the host selector. This means that you can set up 
>>> virtual hosts in the matchtable.xml file, and have sitemaps mounted 
>>> based upon hostname.
>>
>>
>> Mmmh... is it good to mix prefix-based and host-based mounts in a 
>> single matcher?
>
>
> Don't know/don't mind. I'd be happy to have a HostTableMatcher that 
> extends/works with the MountTableMatcher. My desire/need is to see a 
> system that enables me to do host based matching. I could happily have:
> <map:match type="host-table">
> .....
> </map:match>
> <map:match type="mount-table">
> ....
> </map:match>
>
> Thus achieving the same effect, and perhaps more cleanly.
>
> Thoughts? In which case, should the MountTableMatcher be 
> PrefixTableMatcher? Or PrefixMountTableMatcher and 
> HostMountTableMatcher? Hmm.


Yeah, sounds better. They can share some code, but IMO should not be 
mixed in a single class (see also my answer to Unico).

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance  -  http://www.orixo.com