[EMAIL PROTECTED] wrote: > > But most of the stuff is needed to get decent > performance - and to be able to support other protocols > and have better integration with the server. >
- What are the peformance goals? Actual numbers or a percentage improvement goal is something that I would really like to see in the proposal. - Conventional wisdom is that performance tuning code makes it more complex, not simpler. - Layering the code, so that different protocol implementation can be plugged in, is likely to reduce performance. And make the code more complicated. For best performance, you want to skip the layering and framework code entirely and make everything special-purpose. - Better integration with the server makes the code more complex. Integration with multiple servers (like Tomcat 3, Tomcat 4 and Tomcat 5) would normally add quite a bit of complexity. Performance, flexibility and simplicity are at odds with one another. This is a basic engineering truth, and you're going to have a tough time convincing me it doesn't apply here. > There are many things that are hard or impossible with o.a.ajp. > ... > the point is > you can't get too much performance without good buffer management, > byte[], optimized conversions, etc. > Ok, but that's an argument for rewriting o.a.ajp, not for making Coyote the core of Tomcat 5. Is there something about the interfaces defined in Catalina that makes optimizations impossible? -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
