I have a desktop app that stores all it's info in a single XML. The XMl file is read into memory and written to disk when they save. I lock the XML file so that only user can have it open to write. Customers never need more than a few thousand records and it works fine. But some of my customers want to be able to read/update data from more than one PC/Mac on a local network. Performance requirements are low (generally <10 concurrent users and <1 update per second). I don't want to use a heavtwight database. I wondered if SQLite could be a way to handle this? But the SQLite FAQ seems to have quite a few caveats about accessing it from multiple processes across a network. Or is there a simpler/more reliable way to transition a single-user app to multi-user?
This is one of the few cases where I would recommend staying clear of SQLite, because the maintainers are very clear they running it on the network file system with multiple processes is accessing is a bad idea.
