On Thu, 4 Jul 2002, Simon Stewart wrote: > > >The Jetty folks have been working hard on improving the connectivity > > >between apache and jetty and so from 4.1.D2 Jetty has shipped with its > > >own AJP13 Listener. According to Greg Wilkins, the currently shipped > > >version has problems with authenticated and SSL connections, but these > > >are solved in the latest CVS version.
Great news ! > > >Attached is a HOWTO on getting Jetty and Apache 2 talking via > > >mod_jk2. Can I please get some feedback on this? And what do people > > >think about this (or something similar) being included in the next > > >release of the jtc? I agree with Remy the jetty-specific docs should go with jetty. For the native code - I think we can add specific instructions or direct to the right place. > > - It would also give the impression that we're somehow officially > > supporting Jetty in JK 2 or Coyote (we obviously don't), and people > > would bug us with Jetty questions/problems. Well, both jk2 and coyote ( and in general tomcat and jasper ) is open source code that is intended to be usefull and reusable. We can't support or endorse all products that include pieces of tomcat ( enough work in supporting the tomcat release :-), but we should do whatever possible to increase this kind of reuse - it helps us as much as it helps jetty. > > - We also have no buisness advocating Tomcat alternatives. > It really does depend on how you're looking at it. While I can see > your point of view, I believe that your last point is specious. > > Consider the facts: > > 1) Tomcat is an Open Source product. It has no imperative to grab > market share. > 2) Open Source products thrive on collaboration and competition. > 3) The AJP13 protocol, which mod_jk speaks, is openly > documented. Tomcat has a java-side implementation of it. So does > Jetty. The native side is common between both platforms. +1 BTW, it may be a good idea for jetty to take a look at the java side of ajp as well, there are some interesting features. Coyote is quite flexible, and I'm sure it would be easier to adapt it to jetty and take advantage of all jk2 features. And I'm looking forward to code contributions and bug fixes from jetty people. If there's anything we can do to help - please let us know. I don't see jetty as a 'competition' - and I hope they don't either. Our goal is to write a good servlet container and solve 'itches', their goal seems similar. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
