Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 4834 invoked from network); 23 Jan 2009 13:08:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jan 2009 13:08:04 -0000 Received: (qmail 70988 invoked by uid 500); 23 Jan 2009 13:08:03 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 70927 invoked by uid 500); 23 Jan 2009 13:08:03 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 70918 invoked by uid 99); 23 Jan 2009 13:08:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jan 2009 05:08:03 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of covener@gmail.com designates 74.125.44.30 as permitted sender) Received: from [74.125.44.30] (HELO yx-out-2324.google.com) (74.125.44.30) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jan 2009 13:07:55 +0000 Received: by yx-out-2324.google.com with SMTP id 8so1948028yxb.13 for ; Fri, 23 Jan 2009 05:07:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=MdDWs1xEBn+RDeGPk3lRgFo5ef8zHvemo1hjdXVIc7M=; b=nywCq9QRQ7lHtwkCrGqEh7ZrxeR4HAZY6k1duy+fyckoXfWddmV6jq8NdpaVClWa/0 mKw1nBwCP36Rwc3Ejft8bhPkkYGrKEbJ6p8MarVTSxIBrk69m7UZOFvBHfhtHbyAFs0e 1ZAKrCCE67jIHTTVZv0mRVypZd+s35PWuB6Dk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=DglSUWMBnjCbEFk6fXnvK1REmSYO5Ze29JswAT7asftYuFgd099ZqmH/ePKBhSH6Ew SUpKicyyv58TAEsCwLehoxOfJufmTJ2PiNMwqXVoRew0HrqvgaDMzDc0l8F26yDi3FHx 6elOmf9H92fEwogKb1sz1Jkq2/ueyzj1PojU4= MIME-Version: 1.0 Received: by 10.90.53.5 with SMTP id b5mr213839aga.74.1232716036330; Fri, 23 Jan 2009 05:07:16 -0800 (PST) In-Reply-To: <6cca3db30901230442hca333b0n256aebf52b851b29@mail.gmail.com> References: <6cca3db30901230238yd684867p20a980488bc527cf@mail.gmail.com> <4979A970.6090306@sharp.fm> <1f1d9820901230424v743e9325t357d419cc933055@mail.gmail.com> <6cca3db30901230442hca333b0n256aebf52b851b29@mail.gmail.com> Date: Fri, 23 Jan 2009 08:07:16 -0500 Message-ID: <1404e5910901230507x50fe3dbeucbc24ecda7aa9d4e@mail.gmail.com> Subject: Re: APR: Portable across Operating Systems, or Libraries? From: Eric Covener To: APR Developer List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Jan 23, 2009 at 7:42 AM, Greg Stein wrote: > Why? Maintenance cost. Plain and simple. Is there much effort/cost on this front? > Is APR truly used on these other platforms? I've gotta believe there > is some data on that somewhere. http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS208-391&appname=USN > Then, there is the age-old answer, "those edge cases can stick to APR > 1.x and HTTPD 2.x." Modern operating systems would use APR 2.x and > HTTPD 3.x. An alternative is to leave the support in and replace with the other age-old answer, "patches welcome". -- Eric Covener covener@gmail.com