> > I just had to deal with a major change in Apache2.0 -
> > it seems some time ago they reorganized the whole
> > tree,
> > moved apr in a different repository, etc. Is this a
> > different architecture ?
>
> Apache 2.0 is not yet OUT in final... Try to go down in HTTP land and
> build a 1.4 on the ashes of 1.3 but with a whole new architecture.. I
> wonder what the peeps down there would say...
The point was - reorganizing the code doesn't make it
a "different architecture" - and 2.0 is built on top of
1.3 and still shares a lot with it.
> > That's even worse - all the flames that start up
> > whenever code from 4.0 is reused in 3.x. What's the
> > problem ??? Are you afraid of "featurism" ( i.e. are
> > good for 4.0 but bad for 3.3 ) ?
>
> That's TWISTED. Holy shit, you don't even care about supporting our
> users. Jesus Lord! Every single feature you back port from 4.0 will need
> to be supported in BOTH 3.3 and 4.0 and that means doubling our efforts
> in bug tracking and issue solving.
And that's why tomcat3.3 changed to make possible to back port the
features from 4.0 ( and add new feature that are not present in 4.0)
in an independent way, _outside_ the 3.3 release.
> Costin, if you want to work on an evolutionary track, go on and help
> Craig in supporting 3.2 and making it better. If you want to go on your
> own do a 3.3, I don't care what you do in your time. But my -1 stands on
> 3.3 and +1 on bugfixing 3.2.
Let's see:
you have "evolutionary track" between 3.0 and 3.1
Same between 3.1 and 3.2
But suddenly 3.2 -> 3.3 is no longer "evolution" ?
As I said, 3.2 is the middle of the road - I think I made most of the
commits that went into 3.2, and I spent most of this year analyzing
tomcat3.1 and finding the best way to make it faster and cleaner.
Tomcat3.2 is a big step forward versus Tomcat3.1 - but it still have many
issues - take a look at the ContextManager in 3.3, compare it with 3.2 -
there are still many undefined behaviors, even code from 3.0.
> You didn't prove me wrong.
Costin
