Good points from both of you gents. I agree with Vinny that a loading message would be good, but obviously in cases such as Marcel's this is not a solution.
Please mind my ignorance, but why can't Google just keep track of how many requests are coming in and spin up a new instance whenever usage of the current one gets to 80% capacity, or something like that? Are we mainly talking about (what I would call) extreme scenarios where traffic goes up exponentially in an instant, like when tickets go on sale or some such event? On Tuesday, 21 May 2013 22:22:26 UTC+1, Vinny P wrote: > > On Tuesday, May 21, 2013 2:03:05 PM UTC-5, Marcel Manz wrote: > >> ...many of our apps serve other machines in M2M (machine 2 machine) >> communication and I certainly don't want to output any 'Come back later' >> page to a remote API expecting a different input. >> > > Fair enough, I was just throwing that idea out as a temporary band-aid > over the current issue. > > On Tuesday, May 21, 2013 2:03:05 PM UTC-5, Marcel Manz wrote: >> >> Hence all the discussion about using standard frontend instances that >> can handle and scale with load >> > > > Believe me, I'm in your camp. I'd love to see this fixed. > > But a fix isn't going to be out anytime soon, and until it is, I ( and my > users) would appreciate a bit more user-friendliness! > > ----------------- > -Vinny P > Technology & Media Advisor > Chicago, IL > > My Go side project: http://invalidmail.com/ > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
