There is a download all data option for apps, though you do have to
mirror your java classes in python, which is a pain.
A better option would be to port directly in appengine. This is
easier if you know all the table names, but I will assume otherwise.
public void transferNS(String nsFrom, S
Hey Chris,
A couple ideas about how to help us help you help us get better load
balancing.
If it were possible to define different classes of instances to target,
perhaps we could use a request header?
Either an X-AE-Expected-Latency or X-AE-Instance-Class;
The former to let an auto-balancer k
Have you tried copy-pasting the generated ds flat-file,
/war/WEB-INF/appengine-generated/local_db.bin ?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe f
Ok, so I hex dumped my local file, and it has the app id all over the
place.
You may be able to try out the remote api between local installations,
or you're going to need to grep/cat find/replace the app ids in a copy
of your local ds
If you don't like either of these options, write a servle
Appstats is what you are looking for.
http://code.google.com/appengine/docs/python/tools/appstats.html
http://code.google.com/appengine/docs/java/tools/appstats.html
Also look at http://code.google.com/appengine/docs/billing.html
You will see that different kinds of queries and operations use a
Also, take a look at the remote api, as this is exactly what it is
designed for:
http://code.google.com/appengine/docs/java/tools/remoteapi.html
On Dec 6, 11:02 pm, trupanka wrote:
> Please check "Google App Engine Terms of Service", paragraph 4.3
> (athttp://code.google.com/appengine/terms.htm
Do not rely on a frontend instance's RAM-cache. The instances do not share
RAM and the only way you can directly address a particular instance is
using a front-facing backend, as noted by Gerald.
The trouble is, even if you could safely store all your ints in addressable
RAM space, you are goi
I definitely, absolutely love the idea of having appengine internally route
foo.com/api to api.foo.appspot.com. An under-the-covers targeting of
different apps/versions is the only way I can think of to get ssl for the
whole app without having to deal with how browsers handle the
*.appspot.co
Async everything will always save you instance hours. It doesn't matter if
you are threadsafe or not, the async operations allow you to perform a ds /
memcahce / url fetch in a background thread, which you can check on
whenever you want.
Async is extremely useful if you use it to perform "data
