Dear Rob, Dont use the C word... ;)
Yeah, there would need to be some way that the admin priviledged user(s) could unlock/override the locked/open log. In the situation where no concurrent opens can exist this would be neccessary, and even if continously warned that could make the message something that people just ignored... I think that finding an open log could be some sort of flag for this log being open by session (pid) number blah at a datetime with a version number, or some other system to track them. I would suggest also that the option should exist that your RDLOGEDIT works as it does now with NO Concurrent edit checking, should someone simply not care... Thanks Fred et. al for the great ideas. Todd Baker ----- Original Message ----- From: "Rob Landry" <[email protected]> To: "User discussion about the Rivendell Radio Automation System" <[email protected]> Sent: Wednesday, March 7, 2012 7:04:41 AM Subject: Re: [RDD] RDLogedit and Multiple Copies of a Log On Tue, 6 Mar 2012, Fred Gleason wrote: > 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. How can one tell that a log is open? What happens if someone has a log open when rdlogedit (or his or her computer) crashes? Rob _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
