On Friday 13 January 2012 10:47:15 am Aaron Horn wrote: > So the > log is being played out on RDAirPlay in Studio 1 but a user makes > changes to the log in Studio 2 on RDLogEdit - if the user in Studio 2 > saves all their work but then someone in another studio saves also, > their work is lost.
That would be correct !! This is the common problem in trying to implement database replication schemes. In exactly the scenario you describe, the last save is the one that gets saved last, as would be expected, but that's not what you want. You've just opened a paradoxical can of worms. That, or you do lock the database, so that one and only one can be editing at any given time. Now we have another scenario. User two locks the database for edit, and for whatever reason crashes. The database is now perpetually locked. The first thing you'll need to define, is which save is saved, when, where, and why. -- Cowboy http://cowboy.cwf1.com Justice is incidental to law and order. -- J. Edgar Hoover _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
