Costin Manolache wrote:
Let's make it clear - adding new features or replacing/improving any component in tomcat should stay CTR and should be encouraged and supported. Anyone can create Valves, Connectors, Jndi implementations, class loaders or almost anything else that can be plugged into tomcat via config file - and a change to add more hook points shouldn't be hard to get in.
Changes to core components are not mentioned in my proposal, but they could be put under review if needed. Obviously, it seems such changes would be more likely to be put under review, but I don't see a need to make it automatic.
In an earlier email, you mentioned module hooks as an exception. This is interesting, but risky, I think. Hooks is usually a rather important API, and for example, I would think extending the Valve API should be subject to review.
I think it is a big mistake to use the sandbox as a way to avoid confrontation - or to waste time debating subjective things like what is better among 2 not-so-obviously bad solutions ( which is what causes most hurt feelings ). Implement any feature you want in a module, pack it as a jar with instructions on how to use it, get 3 +1s to release it - and after it gets some testing and traction - request it to be part of standard distro or the default JNDI/Connector/ClassLoader/etc. Easy, no conflicts needed, good for both tomcat and the feature itself. If someone else can implement it in a better way - new vote will get the other one.
It's up to the developers to present changes in the best possible way, I think.
Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
