There's more than one way to do things | |
PerlMonks |
How to lock an IO::All::MLDBM objectby DrWhy (Chaplain) |
on Jun 28, 2006 at 01:50 UTC ( [id://557908]=perlquestion: print w/replies, xml ) | Need Help?? |
DrWhy has asked for the wisdom of the Perl Monks concerning the following question:
I have a project that uses IO::All's interface to MLDBM to manage databases of complex perl structures. To this point I have been been guaranteed that only one process will be writing to the db at any one time, so I didn't worry about locking the database during updates. Now, however, I need to add some new features that will break this guarantee, so I need to think about locking.
Does anyone know a good way to do locking on an IO::All::MLDBM object? the ->lock() method doesn't seem to work. It doesn't produce an error, but then any attempt to use the locked object causes one. My assumption then is that locking isn't supported directly by IO::All::MLDBM objects. But maybe I'm just not doing something right?
--DrWhy "If God had meant for us to think for ourselves he would have given us brains. Oh, wait..."
Back to
Seekers of Perl Wisdom
|
|