We need to use file-based persistence instead of DB and very basic operations are in demand: reading/writing/searching/listing and transaction support is a must. I wonder if someone knows whether a framework like this already exists. P.S. Sorry for cross-post to another forum here since I don't know which address is the right one.
WHY can't you use a database. The functions that you have listed are the very reasons that folks use databases instead of files.
"JavaRanch, where the deer and the Certified play" - David O'Meara
Joined: Jun 04, 2001
For very specific reasons I'd prefer no to use a DB. Let's say I manage files uploaded to a server through a web. In this case a client sends a file to the server that stores it immediately on a disk, then another function reads the file and stores it intoe a DB (in a BLOB). To send a file to a client the whole way back is needed. The basic idea is simple. DB is to use search over data it stores. In my case all the data is binary and no search is needed (over the data itself). It's not a problem to write a simple filebased percistence but when transaction comes to the scene it complicates the matter.