My understanding of a warmup request is that it is a request to "prime" a new frontend/backend instance (or do they only apply to frontends?) in preparation of being used at some point in the near future.
My understanding of a loading request is that it is a request to spin-up a new instance because it is needed right now. Hence, it would behoove oneself to try and "warm up" instances ahead of time, to make loading latency that much less.
So my first question is: is my understanding of these request types correct, and if not (or if I'm missing anything noteworthy here), then please begin by clarifying/correcting me!
Next I'm curious: how do you get your GAE server-side code to "handle" a warmup or loading request? Is there a specific interface I need to implement (in Java EE land, you need too implement ServiceContextListener which the web/app container looks for and calls when an app is deployed/started). If so, what is the API for doing so? Otherwise, what is the "entry point" for a GAE app? Basically I'm wondering what class/method should be handling warmup/loading requests.
Last, I ask: what (general) activities should be different in the startup process between the handling of warmup requests and loading requests? Wouldn't they be the same? I ask because I'm interested in using GAE's "Always On" premium feature, and not really sure where I should place my startup code for the instances that will always be on.