Browse Prior Art Database

Exposing object methods and properties for network based distributed applications.

IP.com Disclosure Number: IPCOM000015769D
Original Publication Date: 2002-Sep-30
Included in the Prior Art Database: 2003-Jun-21
Document File: 2 page(s) / 57K

Publishing Venue

IBM

Abstract

The task of firmware providing functionality in a distributed way can be challenging. Client applications of firmware, and firmware it self, desire using firmware functionality without having to understand network details and components. The difficulty of the problem is solved by firmware providing an Object Oriented (OO) Application Interface (API) through exposing its object’s methods and properties to client applications. It is to be noted, for this solution to be viable, the exposed objects require a unique identifier across the differing platforms where the OO objects reside. These identifiers are used as references or handles to the objects within the platform's firmware there by gaining access to the objects exposed methods and properties. In order for an object to expose methods and properties they need to be defined, associated to functional code, and retained for presentation to client applications. For defining methods and properties, methods are defined to have a method name, a method return type, and a list of method parameters, see Figure 1 for a presentation of a method definition. Properties are defined to have a property name, a property type (being the data type), and a property value, see Figure 2 for a presentation of a property definition . These definitions match the Common Information Model (CIM) or Common Information Model definition of a method and property (DMTFs). Definition of a Method

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

  Exposing object methods and properties for network based distributed applications.

  The task of firmware providing functionality in a distributed way can be challenging. Client applications of firmware, and firmware it self, desire using firmware functionality without having to understand network details and components. The difficulty of the problem is solved by firmware providing an Object Oriented (OO) Application Interface (API) through exposing its object's methods and properties to client applications. It is to be noted, for this solution to be viable, the exposed objects require a unique identifier across the differing platforms where the OO objects reside. These identifiers are used as references or handles to the objects within the platform's firmware there by gaining access to the objects exposed methods and properties.

In order for an object to expose methods and properties they need to be defined, associated to functional code, and retained for presentation to client applications.

For defining methods and properties, methods are defined to have a method name, a method return type, and a list of method parameters, see Figure 1 for a presentation of a method definition. Properties are defined to have a property name, a property type (being the data type), and a property value, see Figure 2 for a presentation of a property definition . These definitions match the Common Information Model (CIM) or Common Information Model definition of a method and property (DMTFs).

Definition of a Method

Name Return Type Parameters

Figure 1.

Definition of a Property

Name Type Value

Figure 2.

For associating methods and properties with executable code, an Identifier (ID) unique within an object is used to identify the exposed method or property. The ID is used to associate the method or property definition to functional code. The I...