Hi Ikai, I had this question which I think you answered. Just to confirm: Static file caching works for dynamically generated files as well (such as JSPs). This means that the cached resource does not have to physically exist in the application directories as a static file.
In other words, the static file caching works as reverse proxy (pull) and not like amazon cloud front which requires all the cached files to physically exists and be pushed. E On Jun 3, 2:02 pm, "Ikai L (Google)" <[email protected]> wrote: > You should still be billed for bandwidth. The advantage of using edge > caching is that if the resource is being served from the datastore or > dynamically generated via some other means, you will not incur CPU costs. -- 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.
