Rather than add fuel to the fire, I would like to summarize what I need
out of a servlet engine. Hopefully this will help the members of the PMC
make the correct decisions based off of what users need.
High Priority:
* Stability
We've been running Tomcat 3.1 without any problems for quite a
while now, and it has held well under moderate production load,
as well as very high testing load. The speed could be better,
but its stable.
* Speed
Everybody wants speed, but in a hosting operation such as ours,
the faster the software, the fewer servers we will need to add
to support the load.
* Mature, stable web server connector
This is of utmost importance. We would like for this to have some
features in support of load balancing, but we won't be using it to
actually do the load balancing. An example of this is session
routing. The only load balancers that can handle IP randomizing
proxies and HTTP->HTTPS transitions are SSL accelerators, and
there aren't as many of those on the market as regular load
balancers.
* Virtual Hosting
We need to be able to have the same context names, specifically
the root context, under multiple hosts.
Low Priority:
* Built in HTTP server
We currently use Apache httpd, and will continue to do so for its
flexibility.
* API 2.3
As long as the API is 100% backwards compatible, we don't really
care if it implements 2.3. We just don't plan to implement it for
the time being.
I would also like to say that everybody involved in this flame could be a
little more civil and still make their strong opinions known.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
