Version History of Adobe AIR 2.0.3

Changes in Adobe AIR 2.0.3

  • Adobe AIR 2.0.3 is an update to the Adobe AIR runtime. The update includes improved performance, reliability, compatibility, and security. It is recommended for all AIR users.
  • AIR applications developed for previous versions of AIR do not need to be updated to work with this update.
  • Developers can find additional details about this release by reading the Adobe AIR 2.0.3 Developer Release Notes. Release notes for prior versions of AIR are available at the Adobe AIR 2 release notes page.

AIR 2.0.3 is a runtime-only release

  • Continue to use the AIR 2.0.2 SDK to develop AIR applications. An SDK corresponding to the AIR 2.0.3 runtime will not be released.
  • To verify that a bug in your application was fixed in AIR 2.0.3, you can install the AIR 2.0.3 runtime. Use the ADL -runtime parameter to debug under AIR 2.0.3 (see Using the AIR debug launcher for more information).

Support for HTTP response compression on Windows

  • AIR applications on Windows can now accept HTTP responses compressed with GZIP or Deflate. By default, AIR includes the header "Accept-Encoding: gzip, deflate" with every HTTP or HTTPS request. If the server is configured to compress the response data, network performance is improved. HTTP response compression has been available for Mac and Linux since AIR 2.0.2. Automatically compressing the HTTP request data sent by the application to the server is not supported.
  • Applications must use the AIR 2 (or later) namespace in the application descriptor file to take advantage of HTTP response compression.

Change in timer behavior

  • In previous versions of AIR and Flash Player, timers did not restart the timer interval until any code triggered by the timer finished executing. Thus, if you created a timer to repeat every 500ms, and it took 200ms to execute the code in your timer event handler, then the timer would actually dispatch a timer event every 700ms.
  • As of AIR 2.0.3 and Flash Player 10.1, timers now restart the timer interval immediately. Thus a timer with a repeating interval of 500ms will now fire every 500ms, regardless of how long the code triggered by the timer event handler takes to execute.
  • This change can cause the timers in your application to dispatch timer events more frequently than before. Because the code triggered by the timer is run more frequently, the overall CPU utilization of your application may increase. If this increase is significant for your application, increase the intervals assigned to the timers in your application to compensate.
  • All AIR applications that use timers may be affected by this change when run with the AIR 2.0.3 runtime.