At 12:05 PM 06/26/2001, Cliff Woolley wrote:Anyway, the problem is not 100% solved. We need to make ourselves a new
MMAP to the file that we know won't get deleted.
Why not simply reference count the MMAP/file handle?
I came up with these questions after sending this suggestion:
Where would the reference count go?
- Instead of having an MMAP/file handle, the apr_*_t would have to point to a structure containing the MMAP/file handle, and a reference count. This memory for this structure could not come from any pool with a shorter lifetime than the server itself. It would likely have to be directly apr_malloc'ed.
What about locking?
- For setaside, there should be no other threads knowing about the buckets. The bucket data is just moved to another lifetime, not another thread. As long as the apr type isn't given to another thread, there should be no locking issues.
-- Greg Marr [EMAIL PROTECTED] "We thought you were dead." "I was, but I'm better now." - Sheridan, "The Summoning"
