Hi Philip,
We're already using this caching feature for most of the resources (Images, css, scripts, ...). But the main HTML page is not cached because it can contains user specific information like the email address in case a user logged in. Yes, it could be implemented to cache a default version of the html page for users not logged in and the logged in version is available using another address without using the public caching feature. But this is not what I want because we're planning to implement different features that heavily personalizes the page and users should always be logged in. Caching is not an option in this scenario. I don't know why google doesn't respond to my questions or just increases the limit (only for our app id). We're willing to pay for the increased cpu usage caused by our app but we cannot afford that our service becomes unavailable under heavy load. That's why we began to use GAE! Robert -- 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/-/0-169Q2Fd0UJ. 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.
