Abstract: During an online analytical processing session, actions can be presented for performance on transactional data underlying the session. Actions can be filtered to those valid for a particular context. Other features, such as acquisition of parameters for the actions can be supported.

Abstract: A mobile multimedia framework API is provided that is capable of operation in mobile hardware devices. The mobile multimedia framework API includes a playback interface, controls, an event listener, an error list, exceptions, events, control types, and protocol handlers. Advantageously, a memory size of the mobile multimedia framework API is less than 100 kilobytes.

Abstract: A method and system is provided for customizing Java API implementations. A plurality of class files is obtained, wherein the class files are capable of being used together to provide a plurality of functional behaviors to an application. A feature marker is then associated with each of the class files based on a functionality provided by the class file. Each feature marker indicates a particular functionality provided by the plurality of class files. Particular class files are then selected from the plurality of class files based on the feature markers associated with the particular class files. The plurality of class files can comprise a first JAR file, and the selected class files can be used to generate a second JAR file. The second JAR file can also exclude class files that are not selected. Further, non-Java based native files, if any, utilized by the plurality of class files can also be customized to a subset of the original native files in a similar manner.

Abstract: An invention is provided for creating a mobile multimedia framework API capable of operation in mobile hardware devices is disclosed. All API component access parameters are set to utilize a synchronous programming model. Then, the API components are set to use a pull paradigm, and all master/slave functionality is removed. The resulting mobile multimedia framework API has a memory size of less than 100 kilobytes.

Abstract: An invention is provided for a transport-independent RTP stack. The transport-independent RTP stack includes a transport-independent tasks module, which includes methods that are independent of an underlying transport layer. In communication with the transport-independent module is a connector module, which includes methods that are dependent on the underlying transport layer. In one aspect, the connector module includes data input and output methods, which can be utilized by the transport-independent tasks module to communicate with the underlying transport layer.

Abstract: An invention is provided for customizing Java API implementations. A plurality of class files is obtained, wherein the class files are capable of being used together to provide a plurality of functional behaviors to an application. A feature marker is then associated with each of the class files based on a functionality provided by the class file. Each feature marker indicates a particular functionality provided by the plurality of class files. Particular class files are then selected from the plurality of class files based on the feature markers associated with the particular class files. In one aspect, the plurality of class files can comprise a first JAR file, and the selected class files can be used to generate a second JAR file. The second JAR file can also exclude class files that are not selected. Further, non-Java based native files, if any, utilized by the plurality of class files can also be customized to a subset of the original native files in a similar manner.

Abstract: A mobile multimedia framework API is provided that is capable of operation in mobile hardware devices. The mobile multimedia framework API includes a playback interface, controls, an event listener, an error list, exceptions, events, control types, and protocol handlers. Advantageously, a memory size of the mobile multimedia framework API is less than 100 kilobytes.

Abstract: An invention is provided for creating a mobile multimedia framework API capable of operation in mobile hardware devices is disclosed. All API component access parameters are set to utilize a synchronous programming model. Then, the API components are set to use a pull paradigm, and all master/slave functionality is removed. The resulting mobile multimedia framework API has a memory size of less than 100 kilobytes.