Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Sender: mimo@celeron.mimo.core.pl
Message-ID: <38281893.41DD5B00@interdata.com.pl>
Date: Tue, 09 Nov 1999 13:50:27 +0100
From: Michal Mosiewicz <mimo@interdata.com.pl>
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: Connector -- Context Manager relation
References: <3824AA3D.B3F1C87C@interdata.com.pl>
 <38273D59.DDC9F2A5@eng.sun.com> <382746A9.EC3DF0A1@interdata.com.pl>
 <38275274.DB32FB25@eng.sun.com> <382775DA.D9B2886B@mytownnet.com>
 <38278249.381B5FE6@eng.sun.com>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

costin@eng.sun.com wrote:
> [...]
> About "Host" - what's the meaning of "host" in terms of servlet api, and why
> is it needed? Right now we have the server singleton ( == a tomcat engine instance,
> ContextManger ), and we have Contexts. It is up to ContextManager ( with help
> from Adapter and maybe Interceptors ) to find the right context and invoke service.
> I don't see a need to add a "virtual host" concept into this picture 

As you remember I never liked vhost concept implementations. But still -
if we have the same engine shared for several web servers (we may call
them vhosts), the engine should be able to configure contexts
differently depending on the vhost. I'm not suggesting any specific
implementation, I'm not saying that a class is needed, but I'm just
missing something from this picture.

-- Mike