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.20040817110648.05ff4900@pop3.rowe-clan.net>
Date: Tue, 17 Aug 2004 11:08:56 -0500
To: dev@httpd.apache.org
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Subject: Re: Where is the AJP code...
In-Reply-To: <4121AC2E.2050101@fujitsu-siemens.com>
References: <s120cb95.091@sinclair.provo.novell.com>
 <6.1.2.0.2.20040816180225.05c5ab40@pop3.rowe-clan.net>
 <4121AC2E.2050101@fujitsu-siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:56 AM 8/17/2004, jean-frederic clere wrote:
>William A. Rowe, Jr. wrote:
>>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.
>
>+1

Then let's go ahead, would you please commit the current flavor
of the ajp sources to modules/proxy/  (not modules/proxy/ajp/)
with a commit message to their official source location within
jakarta-tomcat-connectors/ (the real location, not the temporary
ajp/test/ajplib).  Just in case another maintainer wants to look
aside at their development.

Then just a few tweaks so we don't delve the ./ajp/ directory.

Bill