Hi Jeff,
FWIW, the is precisely what we do, but on the Python side. We just multiply
upload copies of our app to the different modules (and then manually flip
all the versions forward - ugh), and then use dispatch to route the traffic
around.
In Python-land, the appcfg.py update command, instead of pointing to a
directory containing code, can point to an app.yaml file (with an arbitrary
name); the code in the same directory as the specified app.yaml file is
what is uploaded to the module.
A conceptual change is that the "global" yaml resources (queue.yaml,
index.yaml, cron.yaml, etc., and the new dispatch.yaml) are never uploaded
with the appcfg.py update command (unless you're using the legacy approach
where you point to a directory). These global resources all need to be
uploaded separately ('update_queues', 'update_indexes', etc.).
Of course, this may be completely different in Java-land, so I'm probably
being of little help except to say that the ability to decompose our
traffic across different QOS modules has made a huge difference to both our
cost and performance.
j
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.
