On Sep 14, 2007, at 11:08 PM, Bill Barker wrote:
Now, I'd prefer that TC is just the Servlet/JSP container
that it is meant to be, and not try to add on proprietary
features. But
that is just me ;).
Others too I think.
Open Source, esp open source at the ASF, has a long and useful
tradition of code being developed to meet the wants and
desires of the individual developers and the dev/user
community around the project. Some faceless corporate
entity doesn't determine what the code looks like,
or what it does, or its future direction, the community
does.
As an example, httpd is designed to be "just" the ref
implementation of HTTP that it is meant to be; but
there is also a plethora of features, enhancements
and "proprietary" features in there, based on what
the developers and users wanted. Is a modular
architecture "required" to impl HTTP? No. Is an
internal filter chain? No. How about the capability
to rewrite URLs on the fly? No. But people wanted
them and people use them and it's one reason why
httpd is a popular as it is and, even more so, why
httpd continues to draw in people willing to work
on and improve the code. I think, personally, if
the TC development environment was seen as a more
friendly and nurturing place, there wouldn't be so
much trouble in people wanting to chip in and help support
things. Instead, they see all the conflict and egos over the
last 5+ years and say "To hell with that, who needs
the aggravation".
As mentioned before, enabling TC to satisfy both,
is a Good Idea, since it satisfies everyone.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
