Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 88236 invoked by uid 500); 9 Dec 2002 10:52:29 -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 88140 invoked from network); 9 Dec 2002 10:52:28 -0000 Date: Mon, 9 Dec 2002 11:52:41 +0100 Subject: Re: APR_TMP_DIRECTORY Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) From: Harrie Hazewinkel To: APR Dev List Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: <56E6B7B0-0B64-11D7-BEB1-0003934A5A7E@lisanza.net> X-Mailer: Apple Mail (2.482) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N HI all, Not to add more oil on the fire, but is it maybe not a reasonable solution - to do the portability parts in only APR and - use APR-UTIL for higher level application functionality (like getting a temp dir from an enviornment variable) ?? This could solve all purposes: 1) application developer do not need to reinvent the wheel, they can use apr-util 2) APR is only portability and make no guesses about the environment as choosing /tmp or ..... The only downside I see is that an application developer cannot use only APR anymore but need APR-UTIL too. cheers Harrie ------------------------------------------------------------------ Author of MOD-SNMP, enabling SNMP management of Apache HTTP server