First of all, thanks very much for quick and reasonable replys! --What is not guaranteed though is a rollback on the --1st update if the second fails or can't happen But it is guaranteed that the 2nd update can be rolled forward once to infinity or the 1st update can be rolled back(probably via a 3rd task) once to infinity. To accomplish that we should configure the queue to retry every e.g. 20 sec. and retring will continue to infinity unless the task is fulfiled. From this perspective my use case can be considered consistent for the duration of infinity. Am I right?
--You have to use distributed transaction as described in --http://blog.notdot.net/2009/9/Distributed-Transactions-on-App-Engine Actually the approach in this article is the same as Didier described except we should manually controll rolling forward(back) in our code. So it is better to use Didier's method because every method doesn't have any advantages over other but Didier's method is more easy to implement. Am I right? Anyway, these methods don't guarante real transactional consistency. And as far I understand there is not any other real transactional solution. Am I right? -- 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.
