Wie im Blog http://googleappengine.blogspot.com/2010/12/happy-holidays-from-app-engine-team-140.html zu lesen, erblickt die Version 1.4 das Adventlicht. Die News in Kürze:
- Always On – For high-priority applications with low or variable traffic, you can now reserve instances via App Engine’s Always On feature. Always On is a premium feature costing $9 per month which reserves three instances of your application, never turning them off, even if the application has no traffic. This mitigates the impact of loading requests on applications that have small or variable amounts of traffic.
Screenshot of the Instances page in the App Engine Admin Console with Always On enabled.
- Warm Up Requests – This feature reduces time to serve requests by anticipating the need for more instances and loading them before user traffic is sent to the new instance. It can be enabled for all applications through app.yaml or appengine-web.xml and is enabled by default for applications that have purchased Always On. Once enabled, warm up requests will be sent whenever possible to load new instances of your application before it begins serving user traffic.
Der erste Teil ist oft unter dem Stichwort Comet geführt.
- No more 30-second limit for background work – With this release, we’ve significantly raised this limit for offline requests from Task Queue and Cron: you can now run for up to 10 minutes without interruption.
- Increased API Call Size Limits – A new API architecture has allowed us to start lifting the 1MB size limits on many of the App Engine APIs. To start, the following APIs have been changed:
- Response size limits for URLFetch have been raised from 1MB to 32MB.
- Memcache batch get/put can now also do up to 32MB requests.
- Image API requests and response size limits have been raised from 1MB to 32MB.
- Mail API outgoing attachments have been increased from 1MB to 10MB
10 Minuten würden mir schon helfen, Daten in die BigTabe zu laden…