COMMON COMPONENT FRAMEWORK
First Claim
1. A computer-implemented method of electronic communication between a component software object and a software container object, comprising:
- initiating a registration function on a container object, passing into said function a first interface pointer corresponding to a generic component interface supported by a component object within the container object;
receiving from the container object a second interface pointer corresponding to a generic container interface supported by the container object, wherein the first and the second interface support a predetermined set of functions for generic communication between a component and a container;
receiving user input on a user interface control running within the component object;
determining a function supported by the container interface associated with the received user input; and
invoking the function in the container interface using the second interface pointer.
11 Assignments
0 Petitions
Accused Products
Abstract
A Common Component Framework (CCF) provides a container interface and a component interface for communication in a multi-tiered software application. Component context data may be transmitted to and from a container describing a current state of a component executing within the container. Context data may correspond to a specific entity (e.g., a financial entity such as a company or stock) identified by a user interacting with the component. The container may communicate the context data between different components to synchronize and coordinate component behavior, providing a more robust and coherent user experience. In addition to component context data, other information may be transmitted between containers and components such as properties, menu options, and data fields, supporting more complete integration of even web-based components into containers.
-
Citations
1 Claim
-
1. A computer-implemented method of electronic communication between a component software object and a software container object, comprising:
-
initiating a registration function on a container object, passing into said function a first interface pointer corresponding to a generic component interface supported by a component object within the container object; receiving from the container object a second interface pointer corresponding to a generic container interface supported by the container object, wherein the first and the second interface support a predetermined set of functions for generic communication between a component and a container; receiving user input on a user interface control running within the component object; determining a function supported by the container interface associated with the received user input; and invoking the function in the container interface using the second interface pointer.
-
Specification