So might I make a humble suggestion. Ask your 65 million customers what they would like in Apache 3.0 - this time around let someone else tell you what they want.
It's the only way to build something. Peter J. Cranstone 5o9, Inc. 303.809.7342 | [EMAIL PROTECTED] Making Web Applications Location and User Aware URL: www.5o9inc.com -----Original Message----- From: Nick Kew [mailto:[EMAIL PROTECTED] Sent: Monday, February 19, 2007 2:44 AM To: dev@httpd.apache.org Subject: Re: 3.0 - Proposed Goals On Tue, 13 Feb 2007 23:33:27 -0800 Paul Querna <[EMAIL PROTECTED]> wrote: > So, I've been kicking around some ideas about where I personally would > like trunk to go for a couple months now. You've missed the most important consideration here. Namely, don't break everything that's gone before. Specifically, a big -1 on forcing substantial rewrites of existing applications. Or in other words, the API must continue to work (with at most trivial breakages). Of course, deprecating things is fine. And where parts of the existing API do not fit well, they might be moved outwards from the core to a compatibility layer - provided that's going to be maintainable. The breakage between 1.x and 2.0 was far too much. If we do it again, the world will rightly conclude that Apache is not a solution fit for the long term. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/