Ok, second round.
People are +1'ing the _goals_ of the proposal, but I the proposal itself doesn't give sufficient detail to determine if the recommended actions will actually lead to those goals being accomplished. Some of the goals even appear to be contradictory, but there's no discussion of the inevitable engineering tradeoffs. Simplicity vs Flexibility is a big issue. For example, the Coyote framework is compatible with Tomcat 3 and Tomcat 4. This is admirable, and may lead to closer ties between the two groups of developers. BUT Coyote is also more complicated and harder to understand than the HTTP connector code in Tomcat 4 that it replaces. It does more, too, but let's face it, it's an integrated framework for writing connectors, and frameworks are harder to understand and build than single-purpose code. That isn't to say it wasn't worth it, but you've gone from only needing to understand o.a.c.connector to having to understand a whole slew of packages and patterns and conventions. There's more buy-in required. I'd like to see considerably more discussion about tradeoffs before the proposal is approved. -- 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]>
