Low-level C file system access is implemented in flascc with a virtual file system API that lets you attach various backing stores so that files can be loaded and saved using different mechanisms. Depending on the backing store used, you can embed files in a SWF, load them from a URL, or load them from a Local Shared Object.



Interfaces
 InterfaceDescription
 IBackingStore This interface describes how an underlying data store interacts with the flascc virtual filesystem.
 ISpecialFile This interface is used by the VFS for special files that must be implemented via code rather than a fixed ByteArray.
 IVFS IVFS describes the interface to the flascc virtual filesystem, which controls how the filesystem appears to an flascc application.
Classes
 ClassDescription
 CheckPath This enum class contains the results determined by the checkPath method.
 DefaultVFS The default implementation of the IVFS interface
 FileHandle This class represents open files available to an flascc application.
 HTTPBackingStore A BackingStore that uses a URLLoader to load its files.
 InMemoryBackingStore The InMemoryBackingStore implements IBackingStore with a memory resident mapping between paths and file data stored as a ByteArray.
 LSOBackingStore Extends the InMemoryBackingStore with one that stores and retrieves its data from a Flash Local Shared object (http://www.adobe.com/security/flashplayer/articles/lso/).
 PathUtils A collection of path handling related functions