On Tue, Nov 21, 2000 at 03:00:01PM -0800, Perrin Harkins wrote:
> On Fri, 17 Nov 2000, Joshua Chamas wrote:
> > I'm working on a new module to be used for mod_perl style
> > caching. I'm calling it MLDBM::Sync because its a subclass
> > of MLDBM that makes sure concurrent access is serialized with
> > flock() and i/o flushing between reads and writes.
>
> I looked through the code and couldn't see how you are doing i/o
> flushing. This is more of an issue with Berkeley DB than SDBM I think,
> since Berkeley DB will cache things in memory. Can you point to me it?
I'm puzzled why people wouldn't just use version 3 of Berkeley DB (via
DB_File.pm or BerkeleyDB.pm) which supports multiple readers and
writers through a shared memory cache. No open/close/flush required
per-write and very very much faster.
Is there a reason I'm missing?
Tim.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
