tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Urban" <jur...@parkcitysolutions.com>
Subject RE: I don?t understand the objective of this open list !
Date Tue, 10 Dec 2002 14:04:06 GMT
> Why waste my time.  I'll vote with my feet and use something else.
> If developers aren't interested in making their software usable by
> writing clear documentation, I won't use it.

Remember, you get what you pay for.  You paid for nothing, you got nothing!
Don't go away mad, just go away (and stop bitching)!

Jim

-----Original Message-----
From: Mike DiChiappari [mailto:mdichiappari@domanisoft.com]
Sent: Monday, December 09, 2002 7:31 PM
To: Tomcat Users List
Subject: Re: I don?t understand the objective of this open list !

>The documentation sure does need some work in certain areas, but it
>is hardly in the sad state that you claim it is in.

Okay, let me give a specific example.  I will describe to you a
likely standard configuration for a server that would be used in a
typical commercial setting.  Prove tomcat can handle this.  Prove the
documentation is available in normal English.  I will also show you
absolute geek-speak in the documentation.

Typical Server Configuration: tomcat serving pages through apache on
port 80 for multiple (virtual) web sites on one web server.  How many
out there have this?  Yes, you can get tomcat up and running on port
8080 very quickly.  How often do you commerical software developers
type http://www.company.com:8080/foo.jsp when visiting commercial
sites?

Problems with the "documentation" (using the term liberally in this case):

1) First, no where on Jakarta's main site is it mentioned that some
type of connector is needed to have tomcat serve page through Apache.
I believe the connectors go by several names (mod_jk, mod_jk2,
mod_webapp, and Catalina being some).  None of these are mentioned or
are listed (there are certainly no links).

2) Lets say one wants to use a relatively new version of software -
say Apache 2.0 with mod_jk2.  There is some nice background info on
mod_jk2 at:

   http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/doc/

Reading through that and links on that page is of little help.
However, there appear to be other useful links on that page.

Configuration info for mod_jk2 is at:

http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/doc/configtce
x.html

This is in the second paragraph, "There is no need to use the jkjni
logic to use normal socket".  Why would one care about "jkjni"?  How
the hell is this even relevant to anything?

Now I could go on and on.  But what is the point.  It is just more
geek speak.  And I haven't even gotten to other situations: running
multiple instance of tomcat, having tomcat run on a different server,
clustering, etc...

Why waste my time.  I'll vote with my feet and use something else.
If developers aren't interested in making their software usable by
writing clear documentation, I won't use it.

Mike

--
To unsubscribe, e-mail:
<mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:tomcat-user-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message