I've been a zone leader with DZone since 2008, and I'm crazy about community. Every day I get to work with the best that JavaScript, HTML5, Android and iOS has to offer, creating apps that truly make at difference, as principal front-end architect at Avego. James is a DZone Zone Leader and has posted 639 posts at DZone. You can read more from them at their website. View Full User Profile

Google App Engine 1.4 Released

  • submit to reddit

Google have announced the release of version 1.4.0 of the popular App Engine SDK. The major feature additions in this release are the Channel API, Always On and Warm Up Requests: 

  • The Channel API - A bi-directional channel for communicating directly with user browsers by pushing notifications directly to the JavaScript running on the client, eliminating the need for polling. This service makes it easy to build real-time applications such as multi-player games, chat rooms, or any collaboration centric app and is built on the same Google infrastructure that powers Google Talk.
  • 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.

On top of these features, Google have works on some of the limitations of existing APIs by changing the limit for background work from 30 seconds to 10 minutes, and by increasing call size limits with response, memsize and image API limits all raised to 32MB, and outgoing Mail API attachments increased to 10MB. 




Andy Leung replied on Fri, 2010/12/03 - 9:24am

The size limit is the top good news to me, I think 30 seconds process time made sense but it would be better to have high boundary and keep small processing time in mind only. Mail attachment increased is a must anyway, who's going to email out with just 1MB attachment nowadays?!

Wait...the task object is still 10kb only though???

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.