Fri, 6 Jan 1995 05:12:01 +0100
|
The problem is essentially the same regardless of what you modify. If you
have multiple owners with the kind of connectivity problem you described,
you want to avoid this kind of scenario:
1. Joe gets list header, planning to change option A.
2. File takes a while to reach Joe.
3. Meanwhile Jack gets list header, planning to change option B.
4. File reaches Jack quickly. Jack updates the list, option B is set.
5. File finally reaches Joe. Joe sets option A and sends the file back,
undoing option B.
6. The next morning, Jack sees that LISTSERV removed option B without
reason or warning, checks his mailbox just to be sure, and reports the
bug :-)
If you know you're the only owner, you can indeed use NOLOCK
systematically.
Eric
|
|
|