> > About why - it's simple, because 2.3 is the next version and to have a
> > future we must keep up to date.
>
> "We" here means you and those who follow you to sourceforge (or
> wherever), I assume?
We means people who use tomcat 3.x or contribute to 3.x - it's not an EOL
product.
I'm not encouraging or asking anyone to "follow" me - what I'm trying to
do is get people to think for themself and develop modules
- if they can get them into apache, that would be great, and I would be
happy to have my modules picked up into the main site and apache.
But developing features and exploring new ideas should be as simple as
possible - and shouldn't require interaction with Jon or alike.
In other words - the goal is to have people turning their ideas
into code and create modules for 3.3.
If anyone will choose to help me or will need my help for their modules
and enhancements - I'll be more than happy. But modules are small things
that can be developed and maintained by people who need them, not
fork-like projects.
> > In any case - I discussed about facade23 just to make clear that I
> > indeed plan to stick around doing 3.x-related stuff ( besides bug fixes ),
> > and to make clear that tomcat 3.x core has a future and will be useful for
> > more people, even post servlet 2.2.
>
> This is an example of what I see as creating confusion. You say above
> that you will take the code outside Jakarta to implement 2.3 etc. And
> then you say here that you will "stick around doing 3.x-related stuff
> (besides bug fixes)." I'm sorry, but you lost me again. If you will go
> ...
Modules. Think about mod_perl or mod_php. Or integration of tomcat into
other programs, or special high-performance or availability modules.
Same model that has been used for Apache.
> jakarta-tomcat repository (often referred to as 3.3-dev), but if this
> code also gets released as Tomcat 3.3, I'm sure your external code
> base and the Jakarta code-base will diverge over time.
The same that worked for apache will hopefully work for 3.3 - again, I
don't want to "fork" ( and check in a copy of tomcat source in a different
repository ). Tomcat 3.3 is the basis, and the modules will have to adapt
to eventual enhancements that will be made on jakarta-tomcat.
I also hope other people will start to develop their individual modules (
and I'm sure that will happen - and it already happens for 3.2 ). That
will give an extra reason for keeping the core backward compatible.
> Or do you mean that you will continue to contribute to the TC 3.x core
> within Jakarta, and only develop the modules externally (under a
> different name)? Sorry if I'm being dense, but I think it's important
> to understand exactly what you have in mind.
That's exactly what I'm trying - and I'm sorry if I can't explain my
thoughts any better. And thank you very much for helping me clarify
things.
--
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
