-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
At 10:10 AM 7/30/99 -0700, you wrote:
>-----------------------------
>Please read the FAQ!
><http://java.apache.org/faq/>
>-----------------------------
>
>> BTW I've been dealing with UNIX installations for several years now, and I
>> have to say that Jserv is by far and away the most difficult thing I've
>> every had to get running. Sendmail, bind, Apache - they're all easy compared
>> to my experience with Jserv so far!
>
>The tools that you mention have all been around for about 5-10 years now
>with thousands of developers working on them. Apache JServ has been around
>for about less than 2 years now with "dozens" of developers working on it.
>Give us a f*cking break. If you want it better, help us MAKE it better.
>
>-jon
One thing that I've observed in watching this list is that the JServ
"powers that be" are very protective of their baby and rather dislike any
criticism. While this is fair, it might be worth at least *listening* to
some of the gripes, as they may point you in the direction of appropriate
improvements. "The customer is always right," eh?
I, too, found that it took *days* to get JServ running. I also found that
"read through your conf files" wasn't a really *helpful* reply, since there
are *so* many ways to screw them up. In my case, the connection really
*couldn't* be made to 127.0.0.1 because I'd messed up ip masquerading. So
the FAQ wasn't helpful.
To me the ripest target for improvement is the error messages. I see that
there are at several different answers in the FAQ-O-MATIC to certain kinds
of observed behaviors, each one saying "THIS is how you fix that problem."
I think if there were some way to get some additional information into the
message logs to help people understand *why* the connection is failing, it
would help build the FAQ better.
Another ripe target would be to work a little more on the parts of the
documentation that describe *how* it all works. This would have two
benefits. First, it would help people diagnose some of their own problems.
Second, it would provide an introduction to the architecture should a
person actually want to dive in and help.
Don't get me wrong, I understand that JServ is a complex product, and that
the small crew of dedicated volunteers is very busy. You are all to be
applauded for your efforts. But if you are assuming that everyone who wants
to use JServ (and wants it to work right) also wants to maintain it and has
the skills to do so, you're delusional. We all specialize, and we assume
that others will specialize in other things. I don't expect you to fight
your own house fires, but I enjoyed it so I got on the volunteer fire
department. While it's nice to be patted on the back for doing something
you enjoy, in the end if you don't enjoy it you need to find something else
to do.
Anyhow that's my $0.02.
-Mike
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
