Dear Didier, Thank you very much for your intention to help. I cannot come the good idea up with using load-on-startup element beside something like having a entity for the number of app instance in datastore and incrementing it in the servlet started up by that, then reading and comparing the entity value from datastore every time before using local cache in the other app instance to decide cleaning up local cache; but this seems to perish the meaning of using cache. Please share your idea with me if you have different idea.
Because memcache already manages integrity of stored data across app instances, there must be the way for such simple task notifying running apps (in different JVMs) about the event of new instantiation of app (in another JVM). The another popular way is to blindly flush local cache periodically at every certain time period. I feel that it's really imperfect way although I may have to take that way until I can find how to hook the event of new instantiation of app. Thank you, Art -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/IpRB0SsG7M4J. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
