>> > - I start a new revolution in tomcat3.2 space ( proposals/something
>> > ), and all the implementation of 2.3 and all controversial stuff
>> > will go there ( i.e. all new features, like dav, http1.1, resource
>> > caching, the new SMTP and POP3 protocols - since any feature will be
>> > in fact just an interceptor plus the implementation itself )
>>
>> Okay, if you feel strongly about not working with the Tomcat 4.x code
>> base. This revolution branch would, however, not change the decision
>> to use the Tomcat 4.x code base for Servlet 2.3/JSP 1.2. The earliest
>> it could be considered would be for the next version of the specs.
>
> Well, if it's a revolution it can implement anything - including 2.3.
> It's not going to be the "RI", of course. Again, support for 2.3 is
> just an independent module that doesn't have to be included in the
> default distribution.
>
Excellent. I think everyone is now on the same page, and that is great.
Costin, the ideas you have for all different types of modules are great,
and I think you need to be the revolutionary behind them. FWIW, for POP
and SMTP, you might want to check out some of the JAMES code, if you
haven't already.
I am personally not against having another choice. As a user, I just code
to the servlet spec, and then use the container that works the best for the
deployment environment (Resin, Tomcat 3.2, Tomcat 4.0, Costin's proposal,
JRun, blah blah blah). From another perspective, we may just see a little
competition in the performance arena, and I think everyone will win with
that.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
