Hans Bergsten <[EMAIL PROTECTED]> wrote:
> "Pier P. Fumagalli" wrote:
>>
>> Sorry for starting what it might end up as a long flamewar, but reading
>> almost 500 emails on the list I ended up a little confused... Also, in a
>> bunch of side discussions, but related always to the same topic, I feel
>> there's something wrong going around here...
>
> Thanks Pier for bringing this issue to a vote. Based on the other replies
> to this mail, it seems to me like the majority wants Tomcat 3.x to be the
> RI for Servlet 2.2/JSP 1.1, with production quality of course, and
> Tomcat 4.x the RI for Servlet 2.3/JSP 1.2. That's what makes most sense
> to me. The devil may be in the details, but I hope we can make it so.
James might be an "instigator", but I'm for sure _THE_ "troublemaker" :) :)
I fully agree with you on that. Let me explain better my position:
I have NOTHING against a Tomcat 3.3 release, if we want to call it 3.3. The
thing I am against is having two different releases of "Tomcat" (3.3 and
4.0) having the same features and capabilities...
I don't want to kill the 3.x tree, nor to abandon it, but I want to see, as
you clearly said 3.x being a 2.2 servlet engine, and tomcat 4.0 being a 2.3
one.
And why is that? Because when people come to http://jakarta.apache.org/ they
have to clearly see what we're doing and decide based on their needs.
Servlet 2.0? Apache JServ (Actually, we might end up moving it to Jakarta as
an "historic" piece of code when Java.Apache.ORG dies)
Servlet 2.1? (fuck, we don't have it, any volunteer?)
Servlet 2.2/JSP 1.1? Tomcat 3.x (3.2, 3.3, 3.4, 3.5 and so on, as long as
there's people willing to deveop it)
Servlet 2.3/JSP 1.2? Tomcat 4.x
Servlet NEXT? When they come out, we'll see what we have in our hands and
we'll decide....
This _IS_ clear....
Pier
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
