Liron Ar has posted comments on this change. Change subject: core: CompensationContext - add support for updated entity only. ......................................................................
Patch Set 1: Actually, why not using a lock? (in the next patch). I started emailing about this issue to Barak, and then I started thinking how can we protect ourselves today without improving the compensation mechanism. So, why can't we use a lock? Yair, There's no reason that the compensation infrastructure won't provide the capabilities needed by the depending modules and it shouldn't force us to synchronize operations if it's unneeded/unwanted. Having a lock or not is a decision to be made by the BLL "layer" in that matter, but there's no reason to not provide this capability by the infra layer- the fact is that we won't always want to lock/restore a delete object. how we use/leverage it on the dependent layer and if locks or needed there is a different issue - let's discuss it on the related patch as it's scenario specific. -- To view, visit http://gerrit.ovirt.org/25231 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I527d8b95b82f76fb4ce0db7e6ec967c23b759524 Gerrit-PatchSet: 1 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Liron Ar <[email protected]> Gerrit-Reviewer: Allon Mureinik <[email protected]> Gerrit-Reviewer: Liron Ar <[email protected]> Gerrit-Reviewer: Maor Lipchuk <[email protected]> Gerrit-Reviewer: Tal Nisan <[email protected]> Gerrit-Reviewer: Yair Zaslavsky <[email protected]> Gerrit-Reviewer: [email protected] Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No _______________________________________________ Engine-patches mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-patches
