ACTIONSCRIPT 3 Developer’s Guide en

ACTIONSCRIPT 3.0 DEVELOPER’S GUIDE
Storing local data
Storing typed objects in shared objects
You can store typed ActionScript instances in shared objects. You do this by calling the
flash.net.registerClassAlias() method to register the class. If you create an instance of your class and store it
in the data member of your shared object and later read the object out, you will get a typed instance. By default, the
SharedObject objectEncoding property supports AMF3 encoding, and unpacks your stored instance from the
SharedObject object; the stored instance retains the same type you specified when you called the
registerClassAlias() method.
Creating multiple shared objects
Flash Player 9 and later, Adobe AIR 1.0 and later
You can create multiple shared objects for the same Flex application. To do this, you assign each of them a different
instance name, as the following example shows:
public var mySO:SharedObject = SharedObject.getLocal("preferences");
public var mySO2:SharedObject = SharedObject.getLocal("history");
This creates a preferences.sol file and a history.sol file in the Flex application’s local directory.
Creating a secure SharedObject
Flash Player 9 and later, Adobe AIR 1.0 and later
When you create either a local or remote SharedObject using getLocal() or getRemote(), there is an optional
parameter named secure that determines whether access to this shared object is restricted to SWF files that are
delivered over an HTTPS connection. If this parameter is set to true and your SWF file is delivered over HTTPS, Flash
Player creates a new secure shared object or gets a reference to an existing secure shared object. This secure shared
object can be read from or written to only by SWF files delivered over HTTPS that call SharedObject.getLocal()
with the secure parameter set to true. If this parameter is set to false and your SWF file is delivered over HTTPS,
Flash Player creates a new shared object or gets a reference to an existing shared object.
Last updated 6/6/2012
707