Return-Path: Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Delivered-To: mailing list dev@apr.apache.org Received: (qmail 14777 invoked from network); 28 Nov 2000 03:27:26 -0000 Received: from kurgan.lyra.org (198.144.203.198) by locus.apache.org with SMTP; 28 Nov 2000 03:27:26 -0000 Received: (from gstein@localhost) by kurgan.lyra.org (8.9.3/8.9.3) id TAA26119 for dev@apr.apache.org; Mon, 27 Nov 2000 19:29:29 -0800 X-Authentication-Warning: kurgan.lyra.org: gstein set sender to gstein@lyra.org using -f Date: Mon, 27 Nov 2000 19:29:29 -0800 From: Greg Stein To: dev@apr.apache.org Subject: Re: SHA1 and Base64 Message-ID: <20001127192929.F25840@lyra.org> Mail-Followup-To: dev@apr.apache.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from rbb@covalent.net on Mon, Nov 27, 2000 at 04:26:46PM -0800 X-URL: http://www.lyra.org/greg/ X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Mon, Nov 27, 2000 at 04:26:46PM -0800, rbb@covalent.net wrote: > > The new-httpd group has discussed putting SHA1 and Base 64 encoding > schemes into APR. This has met with some resistance in the past, but it > really needs to be discussed and decided here. So, can these go in the > passwd directory of APR? They do nothing for portability. They should go into the new "aputil" library in Apache. If we see a big demand for utility functions (rather than portability stuff), then we can extract aputil. Heck, I never thought the inclusion of MD5 was appropriate. That has nothing to do with portability either, and the other parts of APR don't need it. About the only reason is that the MD5 code does translation at the same time. But that is still just a layer on top of APR... nothing in APR uses MD5 itself. (hashes, tables, arrays are portable, but APR itself needs those) This all falls back to the "portability vs. utility" argument. Cheers, -g -- Greg Stein, http://www.lyra.org/