I hope this posting doesn't come across as harsh. I'm just being
pragmatic about what I need to do for the applications I'm currently
running and developing on Google App Engine and for the users on those
applications.
I read the email "Maintenance Schedule for 2009" with some dismay,
the three
One of my apps stopped responding today at around 3pm EST or 12pm PST
for about 5 minutes. Dynamic pages errored on a db timeout and the
static pages took 12+ seconds to respond. The app was in use at the
time so this wasn't a pre-loading issue.
A test version of the app shows a spike on the cr
I'm having problems attaching another developer to one of my Google
App Engine apps.
The first invite went to her Google Apps email account. She created
at Google Account using that email address and can not use the
invite. Essentially the invite link keeps getting her redirected to
the App Eng
I have an application that sends a notification email to users based
upon certain criteria. Unfortunately, I quickly hit the quota limit
since I run this notification once a day and it wants to send the
messages in the cron task.
So my cron task aborts due to quota limits and I'm capped at sendi
The short answer. Don't.
I convinced a client to use GAE and we both regret it. The App keeps
going down at inopportune moments, the scheduled maintenance outages
are in prime time. For the small number of users (about 600) we get
far too many complaints about time out errors. They are rando
spread things out, and retry when sends fail.
>
> -Nick Johnson
>
> On Wed, Oct 14, 2009 at 10:20 PM, Rob Osborne wrote:
>
>
>
>
>
>
>
> > I have an application that sends a notification email to users based
> > upon certain criteria. Unfortunately, I
