On Tue, Mar 9, 2010 at 7:07 PM, Yasuo Higa <[email protected]> wrote: > Slim3 locks an entity group when getting, putting and deleting entities > so that nobody updates the entity group. So it never happens > that the first two entity group transactions commit and the third fails.
What do you do when there is a lock conflict? ThreadA locks Resource1 ThreadB locks Resource2 ThreadA tries to lock Resource2... what happens? Immediate rollback with all locks released? What happens when a datastore error prevents the lock from being deleted? Neat stuff, btw. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
