I'm doing something similar to this using memcache, which is a shared resource across all instances. I want to prohibit some duplicate actions, so the first step is to create a key from URL parameters. If the key is not already in memcache, it's added; on completing the request, the key is deleted. If the key is found on the initial get, the assumption is that this operation is already in progress and we return an error.
This isn't foolproof, but it's sufficient for my needs. On Apr 23, 5:50 am, sisi <[email protected]> wrote: > Hi, > > i'm googling for about a week about a possibility of 'locking' in > google app engine. > Since the instances are spread over different servers, how to > 'synchronise' them? > > I made an app, which access the datastore often, but it is not > suitable for transcations (it is not possible). > How to lock the incomming request, until the actual is finished? > > I found some articles, but none solved it. > Is it possible? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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 > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
