Hi Charlie,
Originally posted by Charlie Goth:
Is this whole approach ok, as the file never gets updated until I save it, is there a requirement(s) (explicit or implicit) that I've missed?
Let's say you have a server S, and two clients C1 and C2. Can each of them (S, C1, and C2) cause the database to be saved? Let's say C3 starts up, makes a couple of updates, and then exits. Then let's say S crashes for some reason. Then C3's updates are lost, aren't they. If you allow clients to force a save then I guess I don't have any objection to your scheme. For example, C4 starts up, makes a couple of updates,
causes the database file to be saved, and then exits. Then if S crashes at least C4's changes won't be lost.
Regards, George
SCJP, SCJD, SCWCD, SCBCD