On Thu, Jul 04, 2002 at 03:57:37AM -0700, Remy Maucherat wrote: > 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. > > > >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? > > -1. > > - Jetty users who are interested in AJP should be able to find the > readme in the Jetty docs.
It's been posted to the Jetty developers too. > - 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. A simple "these aren't the answers you're looking for" would suffice. If that's too much bother, then putting a warning at the top of the README stating that the correct place to go for help may be the jetty mailing lists could be added. There's also an outside chance that the issue the Jetty user has found _could_ be a problem with the native side of the adapter.... > - 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. Can't you see how useful it is that there's a standard way for a servlet container and a web server to communicate at high speed? Without loosing the data that proxying does? AJP has a chance of doing this. Tomcat gets some collaboration on the development of the protocol, and there's some competition because there are two ways of doing the same thing --- one version will undoubtedly be faster or more stable than the other, but there's an obvious incentive to improve both implementations, as well as the documentation of the protocol. Improved documentation of the protocol can only be a Good Thing, since it makes it easier for a newbie to start being useful when providing bug fixes, for a start. Also, the "Not Invented Here" attitude seems a little odd. I believe that you're coming from this as "I'm a tomcat developer, not a jetty developer", but I'm coming at this as "I'm a sysadmin who gets asked to make things happen. Occasionally, I have to use Jetty, occasionally tomcat. They both do the same job, and they both have to sit behind apache. Why should I need to use different tools to connect them together?" There's a chance here to make life a little more pleasent for people on the sharp end. Why not take it? Regards, Simon -- Misspellers of the world untie! -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
