> More choice != more solutions. More fully supported choices == more
> solutions. Very, very stark difference.
AJP is a solution isn't it ? Jetty support AJP isn't it ? More
connectivity, more choices :)
> I'm not interested anymore to be honest. I don't use Tomcat anymore and I
> never will, and these particular instances the client can't be disclosed
> anyway. But if you want to see the way the community communicates people can
> just so look at the mailing lists and see how people are treated. I think
> you have a couple people in particular who are a problem but it spoils the
> whole Tomcat experience. This is why Sun forked Tomcat, and why JBoss is
> even considering dumping Tomcat. This is not an isolated incident.
Tomcat is an old project, with many flams wars.
I'm not sure Sun forked Tomcat about people but because they needed a
larger audience and the Apache audience.
I don't know about JBOSS dropping Tomcat, but it happen, well it's OSS
and Tomcat will find new commiters and new talentuous developpers :)
Incidents would (should) be fixed by Tomcat PMC (and has been allready
discussed there).
> At any rate I don't want to turn this into a Tomcat bashing session. I
> don't use it anymore so it's not really an issue for me. I'm an ecstatic
> Jetty user.
I agree, no flams war, you give me some point, I give you mines
(really consider AJP, I'm in love with mod_jk / AJP) and I just do my
reasonable lobbying :)
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
