Hi Per, I started a thread about issues with having put()s in your on-line handler. Although my initial concern was a little different (how to best confirm writes), it did verge toward the issues I think you are facing.
My conclusion is that any put() to a model with complex indexes will need to be set up in a task queue, and the client code must be designed to handle this (and I do not know what exactly a complex index is, so I'm just avoiding all puts now to any model with moderate and higher use of indexes). Unfortunately, my ill-informed understanding about the many the issues with write times, throttling, etc. is that having puts in your handler module creates the risk of the negative spiral you've described. I'm re-achitecting now. The thread is here: http://groups.google.com/group/google-appengine/browse_thread/thread/c0e44d36d54384a3 Best wishes, stevep -- 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.
