[EMAIL PROTECTED] wrote:
>
> > Yes, but you seem to create a lot of confusion about how and where
> > you will implement support for the new APIs eventually. That, I
> > believe, is one of the main reasons we have the current situation.
> > You said back in November that you where going to start a revolution
> > for the 2.3 stuff, as well as other features. But it never happened
> > and I see hints from you about adding support for the new APIs in 3.3
> > popping up now and then, without a clear indication about when and
> > where.
>
> Then let me clarify, to avoid the confusion - I don't know yet where (
> probably sourceforge or from a homepage ), and I have few ideas about
> "how". I said back in November that I am going to start a revolution with
> the 2.3 stuff and other features - and I didn't do it because finishing
> 3.3 refactoring and merging the fixes from 3.2 should happen first, and
> it's much higher priority.
Okay.
> Since November I learned a few lessons, so I'll not do a revolution - I
> don't think that will give me enough freedom ( and I'll still be at the
> mercy of the PMC ). So it'll be outside apache ( consistent with what I
> said about minimizing my involvment with apache projects ).
Okay.
> 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?
> [...]
> > Well, within the same project it creates a lot of confusion if we
> > have more than one container the same API level. Besides, the Servlet
> > 2.3
> > and JSP 1.2 APIs are backwards compatible, so Tomcat 4.0 by definition
> > supports 2.2/1.1 as well.
>
> And that's not confusing :-)
No. It's the effect of the specifications being backwards compatible,
which is pretty common with specifications; the later version still
supports applications written to the previous version.
> 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
outside Jakarta to continue, it will not be Tomcat 3.3 that "has a
future"
since it will have to be named something else (the Tomcat name is owned
by
ASF). You may start out with the code that today is the HEAD of the
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.
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.
> [...]
Hans
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
