in reply to Re^2: [OT]? Behavior of Berkeley DB cache when reading cached page that was changed on disk by another app
in thread [OT]? Behavior of Berkeley DB cache when reading cached page that was changed on disk by another app

Therefore unless someone can tell me otherwise I think I'm stuck with closing and reopening database connections every time I want to obtain a lock and do work in order to assure that the caching is not invalidated by work done by other processes since the last time I had a database lock.

I won't come out and say otherwise even though I believe so, but I will say, devise a simple test, and test it

Here is a paper of interest Chunk: A Framework for Modular Distributed Shared Memory Systems

  • Comment on Re^3: [OT]? Behavior of Berkeley DB cache when reading cached page that was changed on disk by another app

In Section Seekers of Perl Wisdom