Jim Jagielski <[EMAIL PROTECTED]> writes: > Are people happy with the priority order of the accept mutex? > Right now it's flock -> sysvsem -> fcntl -> pthread. > > I think it should be pthread -> sysvsem -> fcntl -> flock, which > is what 1.3 has...
I realize everybody has jumped in and +1-ed you, but I don't see how you can compare the two orders which you stated above. I would express the current APR default selection (configure.in, line 1303) this way: 1st choice : fcntl 2nd : pthread 3rd : flock 4th : SysV sem I guess I'd vote for this order on systems where we don't have specific knowledge (e.g., use sysvsem for myOS >= x): 1st choice: pthread 2nd choice: fcntl 3rd choice: SysV sem 4th choice: flock Also, in 1.3, I think there is a lot more explicit selection (i.e., case myOS use foo) that needs to be brought forward to APR so that these priorities are irrelevant (they should only be used when we don't have specific OS knowledge). Even if we think we ave the priorities the same between 2.0 and 1.3 it isn't really the same if we don't bring forward the cases where the priorities aren't even used. -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...