> The latter is the only option (short of a synchronized / distributed cache > thingameebob). The mtime isn't going to be fine-grained enough to give you > proper invalidation. Two changes within the same second will cause data > corruption.
... uh.... have you looked at tdb? http://sourceforge.net/projects/tdb it's a multi-read, multi-write 'trivial' database (1024 lines) _with_ locking, with gdb-like API syntax. and it _doesn't_ have data corruption problems on multi-write access. [oh, and it has a shared-mem - mmap - option, too] luke
