Resources | Resources |




Access control list; specify which dynamic applications can access certain settings, directories, or files.
Advanced mobile subscriber software.
Mobile application development platform; versions 1.0 through BREW SDK® 4.0.x
An open, extensible client platform developed by Qualcomm to support system and application software, including personalized and branded user interfaces. May be used with most wireless devices and networks. A component of the BREW System.
Brew MP
Brew Mobile Platform; starting with version 1.0
A flexible operating system platform for mobile devices. It is open and extensible and works with any software ecosystem throughout the global operator and manufacturer communities.
Component application resource file; Lua-based source resource file for BAR, defines resources that are available to the module at runtime.
Component information file; Lua-based source file for MIF, defines resources that a module requires to execute in the Brew MP application execution environment; replaces XML-based MFX format.
A user-defined type that encapsulates data and behavior (i.e. functions) to provide implementation of one or more interfaces it exposes.
A 32-bit globally unique numeric ID, typically in the form of AEECLSID_XXX, that is defined in a BID file generated by the BREW ClassID Generator. ClassIDs are a unique ID given to each class when it is defined, specifying an entry subroutine to create an instance of that class. ClassIDs can also be used as a privilege to use the class.
Embedded file system; file system that resides on a device.
Similar to a C++ abstract base class having only pure virtual methods that provide a specification contract that a implementing class must meet.
Interface ID
A unique ID given to each interface when it is defined in interface header files (or IDL file if using qidl.exe); typically in the form of AEEIID_XXX.
Module information file. A MIF is created by compiling a modulue's CIF and CAR files.
Native store
A settings store for which SettingsReg has built-in support (requiring an implementation of ISettingsStoreFactory). SettingsReg does the reads and writes for a native store.
Non-native store
Non-native stores are managed (read and written) by the application or component.
Private settings
Settings that are available to an application or component on a per-instance basis. No other components or applications can access private settings.

An "execution and protection domain" that defines the set of rights and restrictions to access memory or other resources

Public settings
Settings thatt are made available to the rest of the system via SettingsReg.
Settings store
The storage location for settings.
An implementation of ISettings that provides a unified settings namespace (registry) defined by URIs.
A portion of the SettingsReg namespace that has been claimed by an application or component for its settings.
Uniform Resource Identifier.