One question according to GAE hosting: If your application wasn't requested for some time it is unloaded from memory and first request after that require more time. Is it still apply to static sites?
* [1] http://pages.github.com/
One question according to GAE hosting: If your application wasn't requested for some time it is unloaded from memory and first request after that require more time. Is it still apply to static sites?
* [1] http://pages.github.com/
If the request is going through a static handler (as declared in app.yaml), then the request won't go to the Apps frontend servers at all, it will go to the static file servers. So, no, the app unloading shouldn't be relevant for static files.
I made this diagram for a recent talk that somewhat shows that: http://www.slideshare.net/wuzziwug/writing-apps-the-googley-...
EDIT: It looks like DryDrop may actually use script handlers, not static handlers, in the app.yaml, so app unloading would apply.
But still I think DryDrop may be useful for some folks who want to use GAE for hosting. See the FAQ on http://drydrop.binaryage.com/#faq
You don't need to pay anything for CNAME support now. It was not true previously but now only "obsessed with the idea of running your site on GAE" reason remains.
According to GH pages performance is great.