Mark, I guess I didn't phrase properly since you seem to have misunderstood me:
I want a *separation* of the hosts. Alias, as I understand it, helps to run multiple domains within the same IP-adress. Therefore, I'm using multiple host-elements (one for each IP/domain-combination) to separate them - aka virtual hosting - esp., since they serve different content. @Chuck: > Caldarale, Charles R wrote: > > If you really want to have a separate <Connector> for each site with no > potential for cross-talk, you'll actually need a separate > <Service> element for each. Alternatively, a <Valve> at the <Engine> level > would probably suffice to prevent mixing of IP > addresses and site names. Multiple Service-Elements for me, I guess, would be a show-stopper: If I'm not mistaken, Tomcat's SSO-Valve only works within multiple Engines (as toplevel-element). Since I can't insert a Valve into a Server-Element, there's no SSO-functionality between different Services - am I right with that? Therefore, I guess I stick with my current design having 1 Service, 1 Executor, in there 1 HTTP-Connector for each IP, and I should be on the safe side. Any objections from the gurus? Rgds Gregor -- just because your paranoid, doesn't mean they're not after you... gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
