tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: MinTC, "terrible rudeness", persistence
Date Fri, 19 Apr 2002 13:29:06 GMT

I have to admit not having read the MinTC source, however, I thought the tomcat community
uses/develops multiple implementations of many interfaces. Most of the http/socket/auth?/config
(xml file/ajp-webapp/admin) code is effectively multiple implementations of the same interfaces.
Isn't the whole design of catalina intended to allow different implementations of practically
every concrete class? 

I get the impresssion MinTC is developing different config/bootstrap/resource-location implementations,
but that much of the code is shared as is?

If MinTC was replacing the core processing of Tomcat 3.3 i'd be more inclined to take your
point, as the request chain is much more dedicated and part of the whole, whereas catalina
is just a bunch of nested containers isn't it?

-----Original Message-----
From: Remy Maucherat []
Sent: 19 April 2002 13:24
To: Tomcat Developers List
Subject: Re: MinTC, "terrible rudeness", persistence

> Another (non-committer) +1 for keeping MinTC on tomcat-dev.
> Having a (perhaps limited) web/servlet server in a jar is a great idea.
> If Catalina core, migrates to allow this without a MinTC, other than a
> special server.xml, then that's OK. MinTC will probably have served
> it's purpose, and will die having had an effect probably on the core.

> The only problem I see, is NOT discussing MinTC issues on tomcat-dev -
> having two solutions for this problem is not a bad thing.

I will veto this (or vote against, if it's a majority vote). It has been
very clear for a while that the Tomcat project has to provide one and only
one servlet container for a particular version of the specifications.

If the Tomcat project wants to provide MinTC, it has to be as a proposal for
Tomcat 5.

Note: MinTC is not the same as Catalina. It just happens to use the same
interfaces. It is otherwise a completely different implementation.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

Visit our website at

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message