It seems fixed now, or at least my app's channel feature started working. I agree with Bay, that there should be more test coverage / status reporting. I've been defending GAE even with the recent price increase drama, but it's getting hard with a 9 hour outage addition. My main defense of the price increase is that I don't have to worry about servers breaking down and I can sleep easily. However it turns out that stuff doesn't get fixed in a reasonable amount of time and what's worse, there's a minimal amount of communication from Google on what the hell is actually going on.
On Sep 15, 5:23 pm, Bay <[email protected]> wrote: > Why dont you do what other services do: Write small apps that continously > make sure that all the functions are working in production. Datastore puts, > datastore reads, channel broadcasting, etc... Then you would have really > quickly noticed that an issue was preventing the push-function from working. > > This is probably the third production issue my app have been affected by - > and it always takes 6+ hours to fix. You really, really need to look into > quality assurance. > > No. Really. Its okay that you guys decided to make the whole GAE-platform > highly profitable. You're a company. Its expected. But with downtime like > this on functions that you are going to charge for - that's simply not going > to be acceptable. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
