I understand the concern. This would be just be an option, you would likely not have the same degree of assurance that the item has actually been read without error. Just looking for ways to keep mcycles down which G must be very concerned about based on the low thresholds they have set up for warnings. Based on elapsed time (I can not get mcycle info per call/code unit) it appears puts and deletes probably utilize the most mcycles. I would be fine with this feature even if I lose some data for my purposes. I guess I could skip the datastore entirely for some features and use memcache, which I might do, I just have not had time to play around with that yet.
On Fri, Oct 17, 2008 at 11:24 AM, Josh Heitzman <[EMAIL PROTECTED]>wrote: > > I wouldn't want the item deleted until I had done whatever processing > I needed to do with its data to ensure it didn't get lost due to a > raised exception or crashed machine. > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
