« Using ActiveRecord’s to_xml to produce custom xml including deep level associations
Fork Pools in Ruby on Rails »

Migrating Serialization Changes Within an AIR Application

This post was written by Greg Jastrab. Read other posts by Greg Jastrab.

I just submitted my entry to the AIR Cookbook for the AIR Cookbook Cook-off.

It solves the problem of having your AIR application store an IExternalizable class on disk but then later adding more fields to that class. How would you read the old version of the class without encountering a runtime error if you tried to read the new field that wasn’t present in the older serialization?

Go check it out the cookbook entry to find out how to do this and please rate the article!

About the author: Greg Jastrab joined SmartLogic Solutions in June 2006 and leads all Flash/Flex/AIR development. Follow @gjastrab on twitter

Tags: , , ,

This entry was posted on Thursday, September 11th, 2008 at 1:50 am and is filed under AIR, Flex, Greg Jastrab, Serialization. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “Migrating Serialization Changes Within an AIR Application”

  1. Theo says:
    September 11, 2008 at 9:30 am

    Elegant use of namespaces!

  2. Greg Jastrab says:
    September 11, 2008 at 9:33 am

    Thanks, I’d guess namespaces are probably the most under-utilized feature of AS3.

Leave a Reply