Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (nike.apache.org: 76.96.62.17 is neither permitted nor
 denied by domain of jim@jagunet.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: mod_proxy_html
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: <20111010230258.4f6dd275@baldur>
Date: Tue, 11 Oct 2011 11:39:27 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <2BD32DC0-3085-45F8-AF7B-DCD7E41EF926@jaguNET.com>
References: <20111010230258.4f6dd275@baldur>
To: dev@httpd.apache.org

++1. A great addition for 2.4!

On Oct 10, 2011, at 6:02 PM, Nick Kew wrote:

> Following a chat with a fellow developer, the subject of my
> donating mod_proxy_html to ASF arose again.  This would
> (presumably) sit best as an HTTPD subproject in the manner
> of mod_ftp, mod_fcgid, etc, so that it doesn't pull in
> libxml2 as a dependency for httpd.
> 
> mod_xml2enc, which manages charsets for libxml2-based
> modules including mod_proxy_html, would also be included
> in the subproject.
> 
> I would of course relicense mod_proxy_html at the point
> where it is donated.
> 
> The obvious advantage all round is that we get the benefit
> of Apache infrastructure for collaborative development,
> including patches such as those my correspondent has worked
> on, and opening the way for others such as the derived
> module mod_proxy_content[1] to collaborate more easily
> rather than fork.
> 
> Any interest?
> 
> [1] http://lightyearsoftware.com/2011/02/announcing-mod_proxy_content-1-0/
> 
> -- 
> Nick Kew
>