1. Full text search 2. Memcache objects that get a chance to write themselves to disk if being evicted (yes, this would require some changes to the memcache allocation approach)
3. Faster cold start with Django (I think there are many apps pinging themselves constantly to try to overcome this issue, defeating Google's ability to manage the resources effectively ... with a faster cold start, this would become less problematic. My understanding is that Google compiles the Python files every cold start: perhaps a simple case of precompilation would help and be easy to implement). On Oct 8, 10:37 am, Henrik Lindqvist <henrik.lindqv...@gmail.com> wrote: > 1. CPU cost of datastore writes. This is by far the biggest show- > stopper for any data centric application. GAE is just to expensive! > > 2. The missing java.awt.* classes that is needed to get FOP/iText PDF > generation. Another show-stopper for most enterprise applications. > > 3. HTTPS. Any serious business won't be content using a appspot.com > sub-domain to get HTTPS. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
