Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 35226 invoked by uid 500); 13 Jun 2001 14:50:25 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 35173 invoked from network); 13 Jun 2001 14:50:24 -0000 X-Authentication-Warning: adsl-77-241-65.rdu.bellsouth.net: trawick set sender to trawick@attglobal.net using -f Sender: trawick@bellsouth.net To: new-httpd@apache.org Subject: Re: Apache 2.0 final ? References: <851279708234D3118C7400902762C5A60ED3DA73@gsny26e.ny.fw.gs.com> From: Jeff Trawick Date: 13 Jun 2001 10:42:15 -0400 In-Reply-To: <851279708234D3118C7400902762C5A60ED3DA73@gsny26e.ny.fw.gs.com> Message-ID: Lines: 19 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N "Padwa, Daniel" writes: > Another spin on the same question: when do the core developers (you know who > you are) think that the internal APIs have stabilized enough so that effort > expended porting home-grown modules won't need to be thrown away when 2.0 > settles down? I personally think the API is stabilized enough that little time will be lost further tweaking modules between now and an official 2.0 release. I would expect tweaks to be required, but the many core modules will need any such tweaks too so there should be plenty of examples for guidance. -- Jeff Trawick | trawick@attglobal.net | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...