tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remy Maucherat" <>
Subject Re: MinTC, "terrible rudeness", persistence
Date Fri, 19 Apr 2002 09:31:12 GMT
> I don't known well Tomcat 4
> but I search for a Servlet container which:
> - can be used as a component of an application
>   but does not impose a 'web server' structure
>   to the application
> - is compliant with the latest Servlet standart
>   (~ is an implementation reference)
> - disallows filesystem access
> - still lightweight

MinTC being very similar to Catalina, it wouldn't help A much. I don't know
if it can run with a security manager (point C); it adds significant
complexity, so I could imagine that being left out.
B is ok. I guess it is more lightweight, and hopefully it starts up faster
(point D).

> Thus, I'm interrested in MinTC.
> I'm a newbie but I don't understand
> why it could be harmful for Tomcat 4
> since it seems that MinTC use a big part of Catalina
> and it could thus enhance Tomcat 4
> by the diversified use of its libraries.

As I said, I don't see a need for it. It uses and enocourages to use some
APIs I'd like to attempt to remove or modify in the future (mostly, it's the
Catalina Request/Response API). Of course, it may be already way too late to
be able to fix this (so in the meantime, I've been doing workarounds; that's
Coyote) ;-)

I also still think that Tomcat 3.3 addresses the "market" MinTC wants to
address better (with the very artificial problem of the Servlet API version
support, but this is a double edged sword, as it requires the Java2

Of course, that's just my opinion, I could be wrong.
If many people want to see MinTC here, then it will happen even if I may not
like it.


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

View raw message