On 11/22/2011 3:50 PM, Nick Kew wrote:
On Tue, 22 Nov 2011 22:21:31 +0100
Stefan Fritsch<[email protected]> 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.
There's no reason to deprecate that which didn't ship in a GA release,
simply drop it. That said, there is the entanglement of mod_auth_form.
Redundant API's seem horribly wrong from a maintenance perspective.
But exposing a simpler mod_request style interface to apreq seems like
a win.
