Re^2: How to deal with data race issues with Perl?

I'm leaning towards either asking the user what to do, or to just use the last write as the winner and not worry about it.

The data is not super critical, it's important, but if someone had to do something more than once, it wouldn't be that big of a deal.

Comment on Re^2: How to deal with data race issues with Perl?

Replies are listed 'Best First'.
Re^3: How to deal with data race issues with Perl? by JavaFan (Canon) on Dec 28, 2010 at 16:25 UTC
I'm leaning towards either asking the user what to do, or to just use the last write as the winner and not worry about it. If you're going to ask the user, you'll have to make a UI where the user can edit the conflict. You may want to have a look at various wikis, who have to deal with this as well. If the last write is going to be a winner, just use `git`, with something like `git merge -s recursive -X ours`. (Or `-X theirs`, depending on which way you're merging).	[reply]
Re^4: How to deal with data race issues with Perl? by halfbaked (Sexton) on Dec 28, 2010 at 16:38 UTC
That's an excellent suggestion to look at wikis that deal with this stuff at a much bigger scale than I'll need. I don't want to over-engineer my application, but I'm super curious about how this problem is solved.	[reply]