Hi, How about this approach:
1) define a generic db.model which has two methods get_dirty_bit() and set_dirty_bit(). Hook the put method of the model. 2) If a put occurs set the dirty bit to true in datatore or memcache if possible. The dirty will be a table which will include a simle IntegerProperty() called dirty per _model_. With this we will know the model has been somehow changed from reading a simple Integer property and hopefully from memcache. 3) Render main template call get_dirty_bit() with the specified model, let's say categories in our example. If it is not set, use the previously memcached page, since nothing is changed. If dirty is set read value from the table set dirty bit to False and add the rendered page to memcache. Above seems a simple/efficient approach to cache frequently accesssed pages which has entities that are almost _never_ changes. Any ideas? Improvements or another approaches? Thanks, -- 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.
