> > I agree with Remy the jetty-specific docs should go with jetty. > > Fair enough. Perhaps a pointer to where to find these docs might not > go amiss, though?
We could add an URL in documentation to jetty HOW-TO. > > For the native code - I think we can add specific instructions or > > direct to the right place. > > That would be great. If the "right place" is the README.txt, I'll > happily try and spanner in the relevant information. Do it, at least for jk 1.2.0, but where to put it ? I think we need a README.txt in jtc/jk with misc information about jk (1.2.0), and there we could put jetty ref. > > 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. > > What would be involved in this? I'm starting to get itchy, and though > I've not got much free time atm, in a few weeks things should be > better.... I've not dabbled in the internals of tomcat or coyote yet, > but getting in there and seeing how bits work together is the best way > that I know of to become aquainted with something. Any pointers, > please? > > 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. > > I'll forward your post to some of the Jetty developers. We'll see > where things go from there. I'll be very happy to see jetty dev comments on the tomcat-dev list ;) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
