Developing Flash Lite 2.x and 3.0 Applications

BAR files

You can add, delete, and move files on a BREW-enabled device with a data cable and a Windows application called AppLoader (QUALCOMM provides AppLoader as part of the BREW Tools Suite). However, you cannot copy files from the BREW device that have the extensions .mod, .mif, or .bar to any other device or storage medium. This limitation is enforced by QUALCOMM to ensure that files purchased through the BREW Delivery System (BDS) cannot be distributed to unauthorized users.

To enable Flash content developers to take advantage of this security feature, the Flash Lite player that runs on BREW devices checks for BAR files when it attempts to reference a file on the local device. This restriction applies to any ActionScript or Shared Libraries function that uses a path to reference a file (for instance, loadMovie(), loadSound(), loadVariables(), XML.load(), and so on). To use this feature, developers can append the .bar extension to any files they create, and the player can still locate and display them, but no one can copy them from the BREW device onto which they were initially loaded. The Flash Lite player first checks for the existence of the file by using the supplied local path (for instance, loadMovie(example.swf)). If the file is not found at this location, the player then checks the same path with the .bar extension appended (for instance, loadMovie(example.swf.bar)). The file is then loaded.