Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 12883 invoked by uid 500); 4 Jul 2001 14:58:19 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 12849 invoked from network); 4 Jul 2001 14:58:15 -0000 Message-Id: <4.3.2.7.2.20010704175018.02cc6648@pop3.demon.co.uk> X-Sender: kief_bitbull@kief.demon.co.uk@pop3.demon.co.uk X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 04 Jul 2001 17:58:35 +0300 To: tomcat-dev@jakarta.apache.org From: Kief Morris Subject: RE: PROPOSAL: Tomcat docs In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Robert Slifka typed the following on 09:45 AM 7/4/2001 -0400 >> 2) "" Can't think of a title =) >> ^ >> Tomcat Webdeveloper Guide > >I think we do need to separate out the fact that there are a group of people >who will developing/embedding/extending Tomcat, and a group of people that >will be developing web applications for Tomcat. As a web developer, I don't >care a lot of about Tomcat's internals ;) How about "(Web?) Application Developers' Guide", to more closely map to the servlet spec terminology. For the other bit, maybe "Container Architecture Guide". I think we should avoid the phrase "Tomcat Developer" since, as this mailing list proves, many application developers think that since they are developing on Tomcat, they are Tomcat developers. As a side-rant, "tomcat-dev" is really a bad name for this list (and as a pattern for the other Jakarta lists), since a "Windows Developer" generally is someone who develops for rather than implements the Windows platform, ditto "Java Developer", etc. "tomcat-contrib", "struts-contrib", etc. would be much more intuitive. K