This was discussed previously - conflict resolution is still an issue, and having the ability to work offline on a log is actually rather useful, and would be precluded by this system.
Cheers, James Harrison On 14/03/2012 20:14, Aaron Horn wrote: > On 7 March 2012 01:36, Fred Gleason<[email protected]> wrote: >> I do plan to implement this in the next major version of Rivendell. I >> foresee two modes operation (settable on a per-service basis): >> >> 1) Strict -- Don't allow concurrent editing of logs at all. >> >> 2) Permissive -- Warn the user when about to open a log that is already open >> elsewhere, but allow them to override the warning. > I am more with 2 if we could have a living log - that is a log that > lives entirely in server land with some IPC stuff to tell each client > when changes have been made (updating their screens)? > >> Cheers! > Cheers.. > _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
