1) More control over how Memcache evict entries. More information on Memcache usage (how big, how many entries, how it scale with more traffic). Allow us to purchase more memcache space/slots? Allow us to run some code, call some url, or write data to datastore upon eviction. Basically, anything that help reduce write to datastore. Anything that make memcache as a write-behind cache.
2) Less expensive writes to datastore (api_cpu) 3) Better admin tools for managing data (for Java at least) 0) Making certain task able to run over 30 secs (this is probably on top of everyone list but nobody say it because it most likely won't be allowed) On Oct 6, 2: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 my top three: > > 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 -~----------~----~----~----~------~----~------~--~---