In earlier (around 2009) versions of the ToS that section reads like this:
*You agree not to use the XMPP API to operate or to enable any
telecommunications service or in connection with any applications that
allow users to place calls to or receive calls from any public switched
telephone netw
Hi there,
from the yesterday I started to see a lot of deadline exceptions, memcache
writes exceptions, datastore exceptions - I haven't changed the code from
last 6 month and I've just tried to fix those errors by playing with
idle/automatic instance spinning but its getting just worse (even i
We have released a new version of the experimental Python development
server. We think that it is very usable at this point and has some
significant improvements over the existing version.
To download:
http://code.google.com/p/appengine-devappserver2-experiment/downloads/detail?name=devappserver2-
I am also writing a "pepper script" today.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/J7eDgV8iYqgJ.
To post to this group, send email to googl
At the moment, I have a config that is almost bearable:
I am running 1 idle, 1 max resident. I also have a script peppering the
site with requests once every 10 seconds to keep a dynamic instance alive.
I will be rolling out client side retries on the idempotent REST calls.
I am also moving non-
Went back to 1 min idle instance and everything else to automatic, so now I
have 2 instances billed most of the time.
For the last 27 minutes, we had 20 user-facing loading requests, almost one
per minute.
I can't afford to go back to 4 idle instances and 7 billed instances.
What should I do ?
I had a similar situation with a list of variable length lists of variable
length dictionaries. I used pickle to pack the data into a single
structure. I then sliced the pickled data into smaller (<1MB) chunks and
stored each chunk in an entity which contains a blobstore and a sequence
number.
On
Probably to prevent competition to Google Voice?
Or maybe just there are strict regulations that appengine not willing
engineer for?
On 20 Jan 2013 04:03, "Alpha Scorpii" wrote:
> strange, why this is forbidden in the first place?
>
> On Friday, January 18, 2013 3:49:38 PM UTC+8, Marc Heinken wr
Hello Max,
Definitely the best option is to stick with AppEngine (zero setup +
scaling), then I'd need a paid app with 5+ resident instances as fallback
and some big "max idle instances" to let them sit there running for the
time of campaign.
We're pretty much left with just Python or Go, because
