Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 83248 invoked by uid 500); 11 Feb 2003 10:28:57 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 83235 invoked from network); 11 Feb 2003 10:28:56 -0000 Date: Tue, 11 Feb 2003 11:30:58 +0100 Subject: Re: story posted Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Harrie Hazewinkel To: dev@httpd.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.551) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, Following this thread, I was wondering what the majority thinks is a best way forward. Currently, not many modules are ready for Apache 2.0 regardless the reasons. But it seems already that work is done for Apache 2.1 and people have to port their module again. OK, the module API is almost equal, but to improve adaption first 2.0 needs to be an established entity and with 2.1 the will have a bad signal/noise ratio. Harrie ------------------------------------------------------------------ Author of MOD-SNMP, enabling SNMP management of Apache HTTP server