> My impression was that the locking in Apache::Session is a one-time lock so > it just fixes data integrity issues. So I am not sure if it is fancier than > Cache::Cache unless Cache::Cache has no locking at all (or no concept of > lock choice). What I meant was that since there is a separate locking API used to implement Apache::Session, it should be possible to just use, for example, Apache::Session::Lock::Semaphore without using any other part of Apache::Session. - Perrin
- odd behavior with Cache::Cache brian moseley
- Re: odd behavior with Cache::Cache DeWitt Clinton
- Re: odd behavior with Cache::Cache brian moseley
- Re: odd behavior with Cache::Cache brian moseley
- Re: odd behavior with Cache::Cache DeWitt Clinton
- Re: odd behavior with Cache::Cache DeWitt Clinton
- Re: odd behavior with Cache::Cache DeWitt Clinton
- Re: odd behavior with Cache::Cache brian moseley
- Re: odd behavior with Cache::Cache Perrin Harkins
- Re: odd behavior with Cache::Cache Gunther Birznieks
- Perrin Harkins