Joseph Chiu [mailto:[EMAIL PROTECTED]] wrote:
In my environment, I wanted to force all contexts to be in
the root context.
So, my point is -- if you only need the root context (one
context only!), my
kludge works.
We are presently employing Joseph's elegant (we force root context only)
In our situation, we plan to use multiple virtual hosts, each with its
own root context. That makes the URLs shorter and easier for people to
work with. It also lets you more easily move/copy one context to
another without having to fix all the links.
We use many virtual hosts today in
How? As far as I can tell it's broken in TC 3.1 / mod_jserv. Can you
describe your configuration?
On Thu, 9 Nov 2000, [EMAIL PROTECTED] wrote:
On Wed, 8 Nov 2000, Nick Bauman wrote:
On Thu, 9 Nov 2000, Henri Gomez wrote:
It is important that tomcat3 has a design that allows
umm...it does. i use it.
-Ys-
My understanding is it DOES work for app contexts mapped to a URL like
"/myapp" but it does NOT work
for the root context. "/"
Many of us have webapps that mount to the root context.
I spent WAY to much time figuring this out, I'd love to be proven wrong.
But
On Thu, 9 Nov 2000, Nick Bauman wrote:
How? As far as I can tell it's broken in TC 3.1 / mod_jserv. Can you
describe your configuration?
SNIP
"as advertised" in a web server farm with a rotator box like BigIP. Right
now the Session API in tomcat 3.1 /does not work/ across multiple
On Thu, 9 Nov 2000, Matthew Dornquast wrote:
umm...it does. i use it.
-Ys-
My understanding is it DOES work for app contexts mapped to a URL like
"/myapp" but it does NOT work
for the root context. "/"
Many of us have webapps that mount to the root context.
I spent WAY to much
ubject: Re: No revolution today
On Thu, 9 Nov 2000, Henri Gomez wrote:
It is important that tomcat3 has a design that allows support for
future
versions of the servlet API, but if tomcat developers don't want to see
it
happen - so be it. When Servlet2.3 will be final and i
reOur site (http://www.spun.com) runs multiple Apache servers with load
balancers ("rotator box like BigIP") that distribute traffic over the Apache
servers. We have a farm of Tomcat servers. The session API's work for us.
The only problem is that Tomcat, as distributed, does not allow load
Well, but if you don't need the root-context, then the load balancing
*should* work with other contexts. You are using mod_jserv with APJ
Balancesets, right?
Right Jospeh!
So how important is it to support load balancing of root contexts?
How many users use the root context?
From where I
should be perfectly fine.
Joseph
-Original Message-
From: Matthew Dornquast [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 2:28 PM
To: [EMAIL PROTECTED]
Subject: Re: No revolution today
Well, but if you don't need the root-context, then the load balancing
*should* work
.
If you need multiple contexts without the root context, then the existing
Tomcat should be perfectly fine.
Joseph
-Original Message-
From: Matthew Dornquast [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 2:28 PM
To: [EMAIL PROTECTED]
Subject: Re: No revolution today
the root context, then the existing
Tomcat should be perfectly fine.
Joseph
-Original Message-
From: Matthew Dornquast [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 2:28 PM
To: [EMAIL PROTECTED]
Subject: Re: No revolution today
Well, but if you don't need
On Thu, 9 Nov 2000, Henri Gomez wrote:
It is important that tomcat3 has a design that allows support for
future
versions of the servlet API, but if tomcat developers don't want to see
it
happen - so be it. When Servlet2.3 will be final and in wide use, there
is
nothing that can
13 matches
Mail list logo
