Hi Davy it can be frustrating, but you really should consider to deal with the write delay that you see in dev mode. Like Simon says, while your code might work in production under ideal circumstances 9X% of the time, you don't want it to fail under less ideal circumstances. That's just how GAE works.
On the other hand, I think you have a couple of options that can solve your problem pretty nicely. For example, try a different ORM framework (I started out using JDO, too, but after very many frustrating experiences and limitions, I switched like many others before me). I switched to objectify because I couldn't get JDO's caching to work with my data model. I believe that objectify would also help with your problem, because it will use memcache transparently. I.e. when you write to the datastore your entities should be automatically updated in memcache and subsequent read operations will simply fetch from memcache. Moving away from JDO will save you many a headache... Best, Stefan -- 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.
