[google-appengine] Re: Open Letter to Ryan Barrett and the AppEngine Team regarding "high availability"

2009-09-15 Thread ramu
+1 for this .. I have also been thinking to post something. Though since my app is not mission critical and Failures get corrected by next minute cron update but I still get frustrated when the same entity which was accessed successfully for last 100 times (read only) gets sudden read Timeout Err

[google-appengine] Re: Open Letter to Ryan Barrett and the AppEngine Team regarding "high availability"

2009-09-15 Thread Locke
Your criticism seems legit, I just wanted to point out the following: "* This is a preview release of Google App Engine." It certainly seems that appengine is less mature than some of the other cloud offerings. But it also looks to be more promising over the long term, if they get it right. Comb

[google-appengine] Re: Open Letter to Ryan Barrett and the AppEngine Team regarding "high availability"

2009-09-15 Thread ryan
hi peter! On Sep 15, 3:01 am, gae123 wrote: > Unfortunately, the reality I see and face in the ground for the past > 16 months is different. As I am writing this, I have 2 GAE powered > sites down for TWO DAYS[1] and I am still waiting. The root cause? > Simple "index count quotas" reseting iss

[google-appengine] Re: Open Letter to Ryan Barrett and the AppEngine Team regarding "high availability"

2009-09-15 Thread Stephen
On Sep 16, 12:04 am, ryan wrote: > > (of course, as you mention, we can always > improve the ways we communicate so that you know we're aware of a > problem and do plan to work on it eventually.) How will you do this? --~--~-~--~~~---~--~~ You received this mes

[google-appengine] Re: Open Letter to Ryan Barrett and the AppEngine Team regarding "high availability"

2009-09-15 Thread ryan
On Sep 15, 7:09 pm, Stephen wrote: > On Sep 16, 12:04 am, ryan wrote: > > > (of course, as you mention, we can always > > improve the ways we communicate so that you know we're aware of a > > problem and do plan to work on it eventually.) > > How will you do this? good question. we currently us

[google-appengine] Re: Open Letter to Ryan Barrett and the AppEngine Team regarding "high availability"

2009-09-16 Thread ted stockwell
On Sep 15, 6:04 pm, ryan wrote: > > i also feel your pain in the support department. we wish we had the > resources to provide more high-touch support! we're not a large team, > though, so we have to ruthlessly prioritize. that often means less > individual support, and it can also means priori

[google-appengine] Re: Open Letter to Ryan Barrett and the AppEngine Team regarding "high availability"

2009-09-16 Thread ryan
On Sep 16, 9:10 am, ted stockwell wrote: > > What about opening the SDK code and accepting contributions from the > community? definitely! i assume you mean the java sdk; the python sdk has been open source for a while. we've had good results from that, including useful contributions from the co

[google-appengine] Re: Open Letter to Ryan Barrett and the AppEngine Team regarding "high availability"

2009-09-23 Thread gae123
Hi Ryan, thanks for taking time to reply to my posting and thaks for all the great work that is going on at GAE. I am glad to hear that the indexes problem will be resolved in 1.2.6, it has been one of the few but very acute problems when it happens. I am also content to see that Google has been

[google-appengine] Re: Open Letter to Ryan Barrett and the AppEngine Team regarding "high availability"

2009-09-25 Thread Stephen
On Sep 16, 7:51 am, ryan wrote: > On Sep 15, 7:09 pm, Stephen wrote: > > > On Sep 16, 12:04 am, ryan wrote: > > > > (of course, as you mention, we can always > > > improve the ways we communicate so that you know we're aware of a > > > problem and do plan to work on it eventually.) > > > How