> Ok, so you are going to stop at 3.3 and then what? Abandon things? Hope
> that
> others pick things up? Move to Catalina? What are you going to do?
Costin said he will continue to maintain the 3.3 base. But I think is that
after such objections, he will not start a 3.4 tree (at least not under Apache
Umbrella)
> Tomcat 3.x or 4.x? That is the confusion that needs to be cleared up.
The confusion will exist also for Apache 1.3 / 2.0. And this one will be much
more important.
> The point being that you are duplicating effort. The code is already in
> the future version and now you are back porting it to the past. Why is that
> good?
Again it's not a duplicate effort since differents persons works on different
projects on the /+- same need : a Free Servlet Engine.
> Why is that effort good if people will be moving to 4.x anyway?
You do the judge there. Everybody must go to TC 4.0 ? Who decide that ?
> When the future is 4.x?
The near future is still TC 3.x and it may be a race between TC 3.3 BETAS and
TC 4.0 BETAS. It will be a sane emulation.
> Sure, it is good. I'm not doubting that fact. The reality though is that
> we are moving away from Tomcat 3.x to 4.x.
Again not everybody is ready to go from 3.x to 4.x. I'd like the TC 4.0 design
but it seems to do just to many things. JMX, differents JAXP (lib/server).
> > Better design :-) ? Continuity ?
>
> In your opinion.
The users will decide. Be fair, let them evaluate TC 3.3.
> > I think tomcat 3.x has most of the features that I
> > wanted - I would be happy to see 4.0 using the same
> > patterns and design that allow high performance, but I
> > don't have the time or wish to do it again.
>
> That you wanted. What about what other people want? What about what is
> good for the overall project? Your thinking is very singular.
The overall project is TC 4.0 but TC 3.3 is Costin effort to continue a 3.x
branch. A Future to existing installed site. And as I said before a fast&ligth
servlet-engine (TC 3.3) against a full featured servlet engine (TC 4.0)
> > It's funny you're telling this as if I'm doing
> > something wrong or forking - I strongly agree that
> > forking is bad, and so far I did all I could to avoid
> > forks ( i.e. I stoped developing the Servlet2.3 module
> > as part of tomcat3.3, etc).
>
> > It's the second time an Apache member is asking me to
> > go somewhere else. Believe me, right now it's my
> > biggest wish - I've had more than enough !
>
> I will repeat myself again, since you didn't get it the first time.
> Sigh.
You're just too hard here.
Must we go to vote to see who want Costin stay and who want him stay ?
Could Apache Group could afford to let talentuous developper working on complex
projects fly elsewhere ?
It's seems clear there is scission between pro 3.x and 4.x.
Why not give Costin the 3.x tree responsability (From 3.2.2 to 3.9999) ?
It will let Craig and others Suners (that's the reality) be fully operationnal
on TC 4.x tree (and most of them are paid for). This way more time will be
freed to conduct the TC 4.0 project.
We didn't need a tomcat war OR even worth have Costin and TC 3.3 fly to
sourceforge.
Everybody agreed is does a fantastic works (with limited time and resource).
Having alternative on the same organisation is not a restriction but give more
freedom to final users.
Some will follow TC 4.0 since it will be J2EE, others will develop modules for
TC 3.3 and find it well suited for their need.
There will be Apache 1.3.x and Apache 2.0 sites around the world for many time.
Why not TC 3.x and 4.x ?
What I see is not a question of resource split (if Apache decided to stop TC
3.3 Costin and possiby others will certainly go elsewhere), but a
I'd like to see what Craig think about giving Tomcat TC 3.x to Costin.
Or why not create a new project, HellCat, starting with TC 3.3 code base and
which will be the REFERENCE IMPLEMENTATION of SERVLET 2.2 / JSP 1.1 .
