Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 33871 invoked by uid 500); 23 Feb 2001 18:14:09 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 33517 invoked from network); 23 Feb 2001 18:14:06 -0000 Message-Id: <200102231813.KAA05325@scv1.apple.com> Date: Fri, 23 Feb 2001 12:13:07 -0600 From: "B. W. Fitzpatrick" Content-Type: text/plain; format=flowed; charset=us-ascii Subject: Re: Mixing Apache and Mozilla Cc: Brian Behlendorf , Greg Stein , dev@apr.apache.org To: Jon Smirl X-Mailer: Apple Mail (2.385) In-Reply-To: <025e01c09dc3$30df54a0$0215a8c0@ne.mediaone.net> Mime-Version: 1.0 (Apple Message framework v385) Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Friday, February 23, 2001, at 12:05 PM, Jon Smirl wrote: > > What are the advantages to maintaining two libraries doing the same thing > with slightly different APIs? Portable run-times are a lot of work, NSPR > is > 68KB times the number of platforms it works on. Supporting a portable > run-times is a permanent time sink, every time a new OS version is released > the PR has to be tweaked. I'm sure a new round of tweaking will be needed > for Windows XP. > Are there technical objections to NSPR from the Apache side? > If Apache will come on to the NSPR bandwagon my next target will be > Xerces/Xalan. They're building yet another portable run-time. I think that the main reasons for the resistance you are seeing are: - apr is well along the development path - switching Apache 2.0 from apr to NSPR would set Apache back at least 6 months, and it's already behind schedule. (As Greg pointed out). I think that those 2 reasons far outweigh any technical objections that people might have. -Fitz