I would disagree 100%. You're assuming that priority one for any commercial use of Tomcat is maximizing search engine placement for a given URL. I would be surprised if, out of all the people using Tomcat in a commercial situation, that was priority one for more than .1% or so.
We're selling our applications like crazy, which use Tomcat, but then again, we use Apache as a rule for things on port 80. As far as we're concerned, Tomcat is perfect. John -----Original Message----- From: neal [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 2:18 AM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Well, a few things come to mind. 1. A comparison was made - using tomcat as a web server is like racing a mac truck. Well, for someone new to tomcat and apache (I just arrived from microsoft/iis land) the correct usage pattern was less than obvious ... I just knew that most people used tomcat/apache. I could have never anticipated this sort of issue. If this sort of issue is defended by the community (302s etc) then there should be a blatant disclaimer when downloading the standalone that it is not intended for production use. 2. As to teh chicken and egg analogy - that's a good point - "does theory or an unfortunate reality dictate the direction of the product?" I guess I would defer to point #1. If the product is not going to address the very real issues of production use, it should make it clear to users that it is not indended for production use. Granted the ideal is to sluff off such petty and rediculous issues put forth by the search engine defenses, but at the end of that argument the issue still exists as does the sobering fact that this will be a significant problem for anyone who chooses to deploy a commercial application using the product. neal --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
