Thanks for the replies! Josh's solutions are interesting...I agree with Robert that the extra datastore hits aren't my favorite, but it is appealing for simplicity's sake. And these operations are relatively rare (ie users will not be changing projects very often), so it could be acceptable. Tracking the recent changes is obviously much cheaper...but requires more coding to update and merge in the results from memcache. Sounds like it comes down to a trade-off between simplicity and datastore cost, which isn't too surprising.
At any rate, you confirmed what I thought the behavior would be, and the fact that I do need to come up with a more robust caching solution before switching to the HRD. That's what I needed to know! -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/fdsh_KLwD7UJ. 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.
