Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Tue, 22 Nov 2011 21:50:31 +0000
From: Nick Kew <nick@webthing.com>
To: dev@httpd.apache.org
Subject: Re: Do we want to remove/deprecate mod_request?
Message-ID: <20111122215031.5e55e26f@baldur>
In-Reply-To: <201111222221.31539.sf@sfritsch.de>
References: <201111222221.31539.sf@sfritsch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 22 Nov 2011 22:21:31 +0100
Stefan Fritsch <sf@sfritsch.de> wrote:

> Hi,
> 
> from a cursory glance at mod_request and apreq, it seems that 
> mod_request offers a subset of the functionality of apreq. Graham, is 
> that correct?
> 
> If we aim for inclusion of apreq some time in 2.4.x, it may be a good 
> idea to not add another API for the same thing. Maybe we could 
> document that mod_request is already deprecated?

If it ain't broke ...

IIRC mod_request is a simpler API to work with than apreq, and as
you also say ...

> Removing it now would be a shame because mod_auth_form depends on it.

... it has existing applications.

-1 to deprecating it unless you have compelling technical reasons.
We can remove it at a later date, but if so we should first provide
the compatible API through apreq.


-- 
Nick Kew