Lucian Adrian Grijincu wrote: > > Let's suppose that we have apr_thread_rwlock_create2 > (apr_thread_rwlock_t **rwlock, > > apr_int32_t flag, > > apr_pool_t *pool). > > and we define two flags to create separate types of objects: > apr_thread_rwlock_t which can and which cannot be used in trylock calls. > the performance of the ones which cannot be used in tyolock calls will > be the same on all platforms except for Vista, where we should see some > sort of improvement.
We have this elsewhere in our locking API. It seems like an awkward construct if we use an APR_BLOCKING flag, since it wouldn't be obvious to the casual programmer that it means "we won't _trylock". Maybe a create flag APR_TRYLOCK_MAY_BLOCK?
