Good point. But I don't think of an SLA as the reparations that will be made in case of breach of the SLA, more that is implied that those service levels will, for the most part, be met.
Currently maintenance is scheduled in the middle of prime time, support is best effort, and quality is overall poor. Note that this is NOT incompatible with the current state (Preview) nor is a slight to the (small but hard working and responsive) App Engine team. It's just that those of us who have spent many development hours on the platform would like to see it go to the next level. Soon. On Oct 7, 7:35 am, Jason Smith <j...@proven-corporation.com> wrote: > To people who feel that an SLA is important, I would remind you that > for any serious site, the major cost of downtime is lost availability, > lost business, customer dissatisfaction, etc. A hundred dollar > reimbursement for an hour of downtime is of no consequence. For this > reason, SLAs are not worth the paper they are printed on. > > On Oct 7, 3:26 pm, dflorey <daniel.flo...@gmail.com> wrote: > > > > > 1. Bugfixing (especially Java SDK bugs) > > 2. Enable queries with multiple sortings or find a way to iterate over > > all entities without loosing a sort attribute for __key__ > > 3. Delete entities by query without manually fetching keys and passing > > them back and a real delete * from kind > > > On 7 Okt., 05:38, johnP <j...@thinkwave.com> wrote: > > > > 1. SSL for custom domains. > > > 2. Reliability. What's disturbing is that the same application can > > > work reliably for a while, then it starts working unreliably - based > > > on changes Google makes on the server. > > > 3. A online backup methodology: the ability for us to maintain > > > snapshots of our data, with the ability to roll back to the snapshots > > > as needed. > > > > On Oct 6, 5:22 pm, PointBreak <georgen...@gmail.com> wrote: > > > > > 1. XMPP and WebSockets > > > > 2. XMPP and Flash > > > > 3. XMPP and ways to connect to our bots from inside the browser. > > > > > On Oct 6, 5:04 am, Kenneth <goo...@kmacleod.ie> wrote: > > > > > > I was looking at the issue list the other day. There is a lot rubbish > > > > > in there (support c#!) but what do people who are actively using app > > > > > engine want fixed? If you had to pick three issues what would they > > > > > be? Link to issues only, don't give a "why app engine sucks" > > > > > rant. :-) > > > > > > Here are mytopthree: > > > > > > 1) More granular accounting of how datastore space is > > > > > usedhttp://code.google.com/p/googleappengine/issues/detail?id=1396 > > > > > > This one should be easy, the information is being pulled from > > > > > somewhere already. Right now storage usage is a total black hole. > > > > > > 2) SSL/HTTPS Support on Google Apps > > > > > domainshttp://code.google.com/p/googleappengine/issues/detail?id=792 > > > > > > I know it's a hard problem, but it is really holding gae back. > > > > > > 3) SLAhttp://code.google.com/p/googleappengine/issues/detail?id=501 > > > > > > Release it already, and give us a paid SLA, and a pony. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
