Well it was easy to verify, the ndb indeed utilizes the async trigger's result, which is just beautiful, <3 ndb
I strongly suggest anyone to use this method, it simplifies and improves things a lot, it's really code consuming to get things to prefetch from the client side and then verify that those are indeed the right references, this eliminates the need Also some times you can guess what will be needed inside a function, you can just trigger async gets instead of implementing complex prefetching/caching methods I might even go one step further and stop sending entities to functions and re-fetch them from the cache instead (where practical), what do you guys think? Would it be the same/cached entity 100%? (If there is a chance the entity is re-fetched, it could cause bugs, it would work for read-only entities tho) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
