ISO/IEC 23004-8:2009 pdf – Information technology — Multimedia Middleware — Part 8: Reference software.
1 Scope This part of ISO/IEC 23004 explains the organization of the reference software for ISO/IEC 23004– 1 to 7 (Multimedia Middleware). The electronic attachment to this part of ISO/IEC 23004 provides the source code of the actual software. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 23004-2, Information technology — Multimedia Middleware — Part 2: Multimedia application programming interface (API) ISO/IEC 23004-3, Information technology — Multimedia Middleware — Part 3: Component model ISO/IEC 23004-5, Information technology — Multimedia Middleware — Part 5: Component download ISO/IEC 23004-6, Information technology — Multimedia Middleware — Part 6: Fault management 3 Overview of reference software This is an informative clause. The reference software is organized into directories according to the different parts of ISO/IEC 23004. These directories are: ⎯ 1_Architecture: This directory is rather empty. The architecture is reflected by the implementation of the other parts. ⎯ 2_Multimedia-API: This directory contains the reference implementation of Audio and Video, Governance and IPMP logical components. The Audio and Video logical components are based on UHAPI4Linux implementation. ⎯ 3_ComponentModel: This directory contains the implementation of the core framework, services for remote method invocation (REMI) and services that allow instantiation of services based on a logical component id (Service Manager). The core framework also contains tools that aid in the development of M3W Components (IDL compiler). ⎯ 4_ResourceManagement-Framework: This directory contains the implementation of the resource management framework.
⎯ 5_ComponentDownload-Framework: This directory contains the implementation of the download framework. A framework that enables a large number of scenarios of controlled download / upload of components ⎯ 6_FaultManagement-Framework: This directory contains the implementation of the fault management framework enabling transparent addition of fault tolerance techniques to your software. The implementation consists of policies for intercepting the creation of services and tools for generating wrappers (middleman) that contain the fault tolerance techniques. ⎯ 7_IntegrityManagement-Framework: This directory contains the implementation of the integrity management framework targeted at maintaining and restoring in consistent software configuration on a device in the period that a device is owned and used by a consumer.
4 Multimedia API 4.1 Introduction This is an informative clause. This clause gives a brief explanation on the parts that together form the reference implementation for the Multimedia API of M3W. 4.2 Audio Video 4.2.1 General The directory contains the current release of the reference implementation for clauses 7(general interfaces), 8 (audio interfaces) and 9 (video interfaces) of ISO/IEC-23004-2 (clause numbers are according to the FDIS version). The implementation is based on the UHAPI4Linux implementation that can be found on Sourceforge (www.sourceforge.net). 4.2.2 Building For building instructions please look at: ⎯ 2_Multimedia-API\AudioVideo-API(UHAPI) \HOWTO
4.3 Governance 4.3.1 Introduction The function of Security Manager is to provide secure interaction between M3W Service and external entities. This may include the interaction to acquire Service through download mechanism and invoke Service from remote peer. Security Manager also provides interface for governance/permission checking for accessing M3W Service and/or platform’s resources. 4.3.2 Implementation Currently the implementation consists of one executable component with a SecurityManager service that implements the ISecurityManager interface suite (logical component) and an example client application that uses this service. Service and application are build in the following way: • autoreconf –is • ./configure –prefix=$HOME/local • make • make install Please remember to register the component and its service after installation but before execution of the client application. This is done by the following command: • rcregtool < regscript The registration script “regscript” is generated during the build process.