[Twisted-Python] Lock classes for berkely dbm files

[snacktime]

Anyone have any thoughts on using a lock class (using deferreds)
versus the built in transaction/locking support in BerkeleyDB?

My thought was this.  It sure would be a lot simpler to just use a
lock class and the python built in dbm functions than having to use
the newer bsddb3 module and worry about BerkeleyDb environments and
transactions.

The application is transaction oriented, and each transaction would 
have one write and one read, each in a different lock.

Anyone see any problems with using a lock class in this way?

Chris