> >
> > The future of Tomcat 3.3 seems to be outside Apache now.
> > It's really sad.
>
> Sorry, but that's not what I said Henry. Last month I even came up with
> a proposal that got accepted (but never turned to reality) on how to
> handle this situation... But it seems to me, that everyone here is more
> interested in flaming others rather than read and discuss... And this
> sucks...
>
> I'm not saying to kick the 3.3 proposal out, I'm just saying that, from
> what I see 3.3 is as different from 3.2 as 4.0 is, it is a different
> container. And because of this, rules for revolution and evolution are
> given:
> - old container = bugfixes, improvements (TC3.2)
> - current container = developement (Catalina)
> - new container(s) = proposals (whatever you want for 5.0)
Again ??
Then what about tomcat3.2 - is it as different from 3.1 as 3.3 is from 3.2?
Is there any change in 3.3 that you feel is wrong ? You can send your -1
now, with the technical arguments for that.
I already accepted the -1 on implementing Servlet2.3 - even if it wasn't
on technnical but political reasons, and I'm open to any other changes.
Take the "changes" file, find something you feel is "making 3.3 as
different from 3.2 as 4.0 is" and send it to the list.
Evolution doesn't mean everything is frozen and you make only small
changes here and there. And making tomcat3.3 faster, cleaner and more
modular than 3.2 requires a number of changes.
Generic statements are easy to make - what do you think is part of 3.2
architecture and isn't part of 3.3 ? Yes, some interfaces were removed -
because they were duplicating what Interceptor is doing ( and the
interfaces were introduced after 3.1 for the same reason, making the code
cleaner ).
It's one thing to make the code more modular and cleaner, and another
thing to "change the architecture" and the design patterns.
Costin
