Adaptive interface for cross-platform component generation
First Claim
1. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:
- receive a component request from a client, the component request specifying;
a requested component, the requested component being executable, andan execution context, the execution context comprising;
an attribute that relates to circumstances under which the requested component is executed;
process the received component request to access or generate an interface for the specified execution context for invoking the requested component in the specified execution context and to forward the interface to the client;
generate an adapted component based on the received component request, the adapted component;
having a wrapper that translates input to the component into a format that is understandable by the component and/or translates output from the component into a format that is understandable to the client, andimplementing the requested component;
wherein the component request further specifies one or more local components; and
wherein generating a response to the component request comprises;
analyzing the one or more local components,identifying if there is a missing component, the missing component used by the requested component,where there is a missing component, retrieving the missing component from an external component library, and adding the missing component to the adapted component; and
execute the requested component.
1 Assignment
0 Petitions
Accused Products
Abstract
Exemplary embodiments provide adapted components that may be used by a computer program under different execution contexts. The adapted components may include platform independent source code which may be executed regardless of the execution context in which the component is deployed. Adaptation logic may wrap the execution context independent component in a wrapper. The wrapper may perform data marshaling between the execution context independent component and a computer program invoking the execution context independent component, or the host system on which the computer program is deployed. The execution context independent component may be adapted to a new execution context dynamically the first time that the execution context independent component is invoked in the execution context. Thereafter, the execution context independent component may be invoked statically without the need to re-adapt the component.
-
Citations
20 Claims
-
1. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:
-
receive a component request from a client, the component request specifying; a requested component, the requested component being executable, and an execution context, the execution context comprising; an attribute that relates to circumstances under which the requested component is executed; process the received component request to access or generate an interface for the specified execution context for invoking the requested component in the specified execution context and to forward the interface to the client; generate an adapted component based on the received component request, the adapted component; having a wrapper that translates input to the component into a format that is understandable by the component and/or translates output from the component into a format that is understandable to the client, and implementing the requested component; wherein the component request further specifies one or more local components; and wherein generating a response to the component request comprises; analyzing the one or more local components, identifying if there is a missing component, the missing component used by the requested component, where there is a missing component, retrieving the missing component from an external component library, and adding the missing component to the adapted component; and execute the requested component. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A computer-implemented method comprising:
-
receiving, using one or more processors, a component request from a client, the component request specifying; a requested component, the requested component being executable, and an execution context, the execution context comprising an attribute that relates to the circumstances under which the requested component is executed; processing, using the one or more processors, the component request to access or generate an interface for an execution context for invoking the requested component in the execution context and to forward the interface to the client; generating, using one or more processors, a response to the component request, the response comprising an adapted component, the adapted component; having a wrapper that translates input to the component into a format that is understandable by the component and/or translates output from the component into a format that is understandable to the client, and implementing the requested unit of functionality; wherein the component request further specifies one or more local components; wherein generating the response to the component request comprises; analyzing the one or more local components, identifying if there is a missing component, the missing component used by the requested component, where there is a missing component, retrieving the missing component from an external component library, and adding the missing component to the adapted component; and executing the request component. - View Dependent Claims (16, 17, 18, 19)
-
-
20. A system comprising:
-
a non-transitory storage medium storing; a library of components; and one or more processors configured to; process a component request from a client to access or generate an interface for an execution context for invoking the requested component in the execution context and to forward the interface to the client, the component request specifying; the execution context comprising an attribute that relates to the circumstances under which the requested component is executed, and a requested unit of functionality; identify a target component in the library, the target component compatible with the component request; generate a response to the component request, the response comprising an adapted component, the adapted component; having a wrapper that translates input to the component into a format that is understandable by the component and/or translates output from the component into a format that is understandable to the client having been generated from the target component, implementing the requested unit of functionality; wherein the component request further specifies one or more local components; and wherein generating the response to the component request comprises; analyzing the one or more local components, identifying if there is a missing component, the missing component used by the requested component, where there is a missing component, retrieving the missing component from an external component library, and adding the missing component to the adapted component; and execute the requested component.
-
Specification