Does anyone have an argument for preventing concurrent writes to the database as long as they are different records? In other words, record locking prevents two clients from modifying the same record, but there would be nothing wrong with having two clients (threads), each using their own RandomAccessFile object to modify different parts of the same file since all records are fixed length.
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads