On Jan 13, 2012, at 10:47 15, Aaron Horn wrote: > To me the solution is to remove the 'save' button and have any changes > reflected live on every computer with that log open in an immediate > sense.
This merely pushes the basic problem down a level. You'll still have users nuking each other's changes, not to mention that there are times that you don't *want* a change saved system-wide, but only locally. > Either that or lock logs (e.g. 'this log is being edited at location xyz, > please close there before editing the log'). Yes, some sort of locking will be required to resolve this sort of thing, either at the level of entire logs or some section thereof (e.g. 'morning drive', 'middays', 'afternoon drive', etc). Infrastructure-wise, two things are required: 1) A way to assert a system-wide lock 2) A way to detect and break stale locks (e.g. after a system that has created a lock dies unexpectedly) Number 2) is the more difficult of the two. Optimally, some sort of inter-workstation IPC would do the trick, although writing and polling a timestamp in the DB might be viable as well. Not a trivial undertaking, either way. Cheers! |-------------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-------------------------------------------------------------------------| | A room without books is like a body without a soul. | | -- Cicero | |-------------------------------------------------------------------------| _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
