it occured to me this is the same type of problem as a distributed database commit
therefore the race conditon can be fixed by using 2-phase commit which does imply extras pin for commit and abort; -change/-changed and -prepare/-prepared representing the voting phase of 2PC, the commit pin signaling final commit, the abort pin signaling a rollback the good news is that as far as I can see at this point, a toolchanger sticking to the old behaviour and ignoring the commit and abort pin will continue to "work" (including race condition, that is, because it bases its behaviour on the voting phase result only) I have a tentative design but it needs a bit more shaking out before posting -m ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
