apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@attglobal.net>
Subject Re: apr_lock.h lock scope question
Date Mon, 25 Jun 2001 15:32:34 GMT
Aaron Bannert <aaron@ebuilt.com> writes:

> > *There would have to be an intermediate routine for APR_LOCK_ALL on
> > most platforms when APR is built with thread support.
> 
> I still disagree with apr_lock_*() providing both
> INTRAPROCESS and CROSS_PROCESS  *in the same function calls*.

If you don't have them both in the same function calls then how do you
implement APR_LOCK_ALL?  It is nice to have APR_LOCK_ALL 'cause that
handles a portability/performance issue on behalf of the application.

-- 
Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...


Mime
View raw message