Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 3560 invoked by uid 500); 13 Apr 2001 03:09:47 -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 3533 invoked from network); 13 Apr 2001 03:09:46 -0000 Sender: minfrin Message-ID: <3AD66D62.82C812DA@sharp.fm> Date: Fri, 13 Apr 2001 05:07:14 +0200 From: Graham Leggett X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.18 ppc) X-Accept-Language: en MIME-Version: 1.0 To: new-httpd@apache.org CC: modproxy-dev@apache.org Subject: Re: httpd-proxy status References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Chuck Murcko wrote: > Based on interest at the hackathon, we'd like to present this for a vote > for reintegration soon. But we'd like to get it working properly first. > 8^) ...and compilation tested on all the platforms supported... > Bear in mind that the -current mod_proxy development is only part 2 of > the 3 part plan: > > 1) support 1.3.x > 2) support a cacheless 1.3.x workalike in 2.0 Done - right now we are looking for bugs. > 3) redesign to be a multiprotocol router in 2.0 We should be there already - as of now we can (if not then bug) deliver content hosted on both a webserver and an ftp server, in addition to the normal deliver content from filesystem and executable binary (CGI). I have plans to include the ability to serve LDAP URLS as well - allowing you to serve pages directly from attributes in an LDAP server. (The need I have is to embed LDAP attributes in a page, using an LDAP MPR and mod_include, instead of the klunky CGIs I use right now). Heck, even SQL is a possibility :) Regards, Graham -- ----------------------------------------- minfrin@sharp.fm "There's a moon over Bourbon Street tonight..."