apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@attglobal.net>
Subject Re: cvs commit: apr STATUS
Date Wed, 26 Dec 2001 01:19:19 GMT
Justin Erenkrantz <jerenkrantz@ebuilt.com> writes:

> > Maybe we should try to acquire/release the lock during create time,
> > and return the acquire errno if that fails.  Maybe the error codes
> > differ between systems but at least we fail ahead of time.
> > 
> > That sounds easy and harmless to me.  Any improvements to this?
> I'd like to see this as a lock creation option.  Something like
> a flag - say, APR_LOCK_VERIFY or some such.  I don't think we should
> do the acquire/release unless asked for by the caller.  I think
> this might mean changing or extending the lock creation APIs -
> thoughts?  -- justin

Why would it need to be an option?  Are you concerned about the

(I wonder how expensive it is, particularly when compared to the
overall cost of creating a file-based lock.  I'd guess that it isn't
very expensive, but I really have no clue.)

Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
             Born in Roswell... married an alien...

View raw message