Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Errors-To: <wrowe@rowe-clan.net>
Message-Id: <6.1.2.0.2.20040816180225.05c5ab40@pop3.rowe-clan.net>
Date: Mon, 16 Aug 2004 18:03:44 -0500
To: dev@httpd.apache.org
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Subject: Re: Where is the AJP code...
Cc: <dev@httpd.apache.org>
In-Reply-To: <s120cb95.091@sinclair.provo.novell.com>
References: <s120cb95.091@sinclair.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 03:58 PM 8/16/2004, Brad Nicholes wrote:
>   The addition of the proxy_ajp module to the httpd project presents a
>build problem.  The AJP module code exists in httpd/modules/proxy in the
>httpd project but the AJP lib code still sits in the
>jakarta-tomcat-connectors\ajp\ajplib\test in the jakarta project.  Is
>the AJPLIB code going to be migrated to the httpd project?  Why is the
>AJPLIB code in a test directory?

I'm +1 for placing it in modules/proxy/ ... iff it will be maintained
and kept up to date.

If not, assuming that lib location is wrong - it should become
an autoconf option.

Can we trust that ajp lib c sources will be kept in sync?

Bill