RE: future questions
Another overwhelming diplomacy lesson... I guess. Have fun, Paulo Gaspar -Original Message- From: Jon Stevens [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 20, 2000 01:21 To: tomcat-dev Subject: future questions Lets see how many of these questions come up in the future by users: I downloaded the latest J2EE and it includes Tomcat. However, when I looked on your website, it says that you have two versions of Tomcat. Which one comes with J2EE? Which one should I be using? I found a bug in 3.3. When is the next release going to happen? (Implying that we are going to have to continue on putting effort towards more 3.3.x releases.) I found a *serious* architectural issue in 3.3 that warrants a 3.4 release. What should we do now? (Implying that we are going to have to continue on putting effort towards more 3.3.x releases.) I looked at your website and there are two versions of Tomcat, which one should I use? They both seem to be in active development. Why is one better than the other? p.s. Costin, I had a great idea. I'm going to forward to you all of the personal email based Tomcat support questions that I get. Have fun answering them. :-) -jon
RE: future questions
From: Jon Stevens [mailto:[EMAIL PROTECTED]] snip p.s. Costin, I had a great idea. I'm going to forward to you all of the personal email based Tomcat support questions that I get. Have fun answering them. :-) How about forwarding them or pointing them to the tomcat-user list where these questions will be answered? -Dave
Re: future questions
on 12/19/2000 4:26 PM, "David Rees" [EMAIL PROTECTED] wrote: How about forwarding them or pointing them to the tomcat-user list where these questions will be answered? -Dave Because not everyone wants to subscribe to a mailing list to just get a simple question answered. -jon
RE: future questions
1+
The problem, of course, is that the critical functionality is evolving so
rapidly, that most "users" prefer the developer list, since that is where
the action is. This is the downside of a Open Source project such as Tomcat
(as opposed to the Apache Server project where CVS updates involve very
little change in the functionality, or usability of the server).
The alternative, as some implied, is to understand that the "developers"
group is going to consist of active contributors to the CVS codebase as
well as "active" alpha/beta testers looking to get a head start with what
is a cutting edge product, but not up to speed with the philosophical
underpinnings of the evolution of the system. They, by the way, are likely
to be the first real "users" of the "product" and their questions, concerns
and frustrations an indication of the likelihood of the product being
accepted.
Besides the current traffic on tomcat-dev is hardly so high as to suggest
these users pose a risk and one can simply ignore questions one doesn't
want to answer which is much less typing than biting someone's head off for
not having been here three months ago.
Sean
PS. Being on a couple of NNTP based newsgoups, I think I favor these to a
mailing list since it is easier to thread (and ignore) messages.
"David Rees"
drees@ebetinTo: [EMAIL PROTECTED]
c.com cc:
Subject: RE: future questions
12/19/00
07:26 PM
Please
respond to
tomcat-dev
From: Jon Stevens [mailto:[EMAIL PROTECTED]]
snip
p.s. Costin, I had a great idea. I'm going to forward to you all of the
personal email based Tomcat support questions that I get. Have
fun answering
them. :-)
How about forwarding them or pointing them to the tomcat-user list where
these questions will be answered?
-Dave
Re: future questions
Hi again, Jon. I downloaded the latest J2EE and it includes Tomcat. However, when I looked on your website, it says that you have two versions of Tomcat. Which one comes with J2EE? Which one should I be using? I'm sure J2EE will have a README telling you what version it includes. As for "what version should I be using " - the one that works best for you. ( should I use RedHat Linux or Mandrake ? Win 98 or Win NT ? ). I found a bug in 3.3. When is the next release going to happen? (Implying that we are going to have to continue on putting effort towards more 3.3.x releases.) It's an open source project. And it seems you are not putting any effort into 3.x anyway, but yet it works fine, so don't worry about it. I found a *serious* architectural issue in 3.3 that warrants a 3.4 release. What should we do now? (Implying that we are going to have to continue on putting effort towards more 3.3.x releases.) Again, I'm sure people working on 3.3 will find a way to deal with that. My preference is to stop changing the core API and architecture after 3.3 is out, but it seems I'm not the only developer on 3.3, and if something serious happens I'm sure we ( as a group ) will take a good decision. I looked at your website and there are two versions of Tomcat, which one should I use? They both seem to be in active development. Why is one better than the other? I can speak about why tomcat 3.3 is better, but I don't want to open yet another fight. So let's say: there are 2 ideas and 2 different implementations. They both share a lot of code ( the connector, modules, etc) but have slightly different core and architecture. It's a perfect example of how you can componentize and build with components, and how code reuse is good - tomcat3.3 will try to reuse as much as possible from 4.0, and I hope the reverse will be true. ( unfortunately, this is not true as of today, with 4.0 having a completely different codebasse - except jasper, which is a great example of how development should work - and tomcat3.3 just starting to reuse code from 4.0). I have great hopes for mod_webapp and mod_jk to be a first example of sharing, and I'm sure there are other areas as well. p.s. Costin, I had a great idea. I'm going to forward to you all of the personal email based Tomcat support questions that I get. Have fun answering them. :-) Thanks, I already get a lot, and sometimes I do have fun answering them ( when I have time to do so ). Costin
