[appengine-java] Re: is it possible that repeated task executions happen in parallel ?

I asked this question a while back and didn't really get a definitive response. https://groups.google.com/d/topic/google-appengine/YRAK6lHV1XQ/discussion (that's the link groups is giving me, but I'm having trouble with it - title of the thread is 'Idempotence multiple task execution' if you

[google-appengine] Re: is it possible that repeated task executions happen in parallel ?

I asked this question a while back and didn't really get a definitive response. https://groups.google.com/d/topic/google-appengine/YRAK6lHV1XQ/discussion (that's the link groups is giving me, but I'm having trouble with it - title of the thread is 'Idempotence multiple task execution' if you

Re: [google-appengine] Re: App Engine SDK 1.4.2 is out!

Thanks Greg - would it be a future possibility to configure the queue algorithm not to do this (on a per-queue basis)? Obviously the low latency heuristic is a good one in most situations, but an app developer might be prepared to wear a slight variation in latency to get guaranteed

[google-appengine] Re: App Engine SDK 1.4.2 is out!

Thanks Ikai - great release! One question, can a queue that is rate limited to 1 concurrent task be seen as a FIFO serialised queue? i.e. is order guaranteed, even if the current running task fails it goes back to the front of the queue? I'm guessing you don't guarantee this behaviour but

Re: [google-appengine] Re: using allocate_ids() for other purposes

Thanks guys - that helps a lot. Cheers, Colin -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to

[google-appengine] using allocate_ids() for other purposes

I'm considering the possibility of using the datastore's allocate_ids() as a generic mechanism to maintain persistent counters. I figure this will probably be a dumb idea, but thought I'd pose the question anyway. Here is some code - keys = db.allocate_ids(db.Key.from_path('SomeCounter',

[google-appengine] Re: using allocate_ids() for other purposes

Thanks for the info Calvin. I'm not too worried about the call being RPC slow, and I won't need to use it inside a transaction :) Looking at discussions elsewherehttps://groups.google.com/d/msg/google-appengine-python/_AVE7D4P8tY/agOmNAOPSdYJ, it would seem they should be reliably sequential

[google-appengine] Re: Drools and Jess Expert system Develpoment with Google App Engine

Perhaps this post will help - http://drools-java-rules-engine.46999.n3.nabble.com/drools-and-google-app-engine-td64871.html, I seem to remember something about those libraries requiring some unexpected stuff that interfered with Java security policies, but the memory is pretty faint - a quick

[google-appengine] Re: Why do my indexes stay Building for long periods of time?

They do take a while - there appears to be a really long queue before the queue indicated there. A couple of hours in the state you have shown there is not uncommon, although they have been getting better recently. So if you have some critical functionality to deploy that needs a new index, you

[google-appengine] Re: Storing properties dict as db.Model field

http://stackoverflow.com/questions/3203543/how-to-make-persistent-a-python-dictionary-on-google-appengine/3203672#3203672 I'm still pretty convinced my answer was the best - especially since it borrows nick johnson's code :) Cheers, Colin -- You received this message because you are