Dynamic component transfer
AssigneeSap SE
InventorAlexander Gebhart
Life of this patent
Estimating the term…
Abstract
Methods and apparatus, including computer program products. In one embodiment, a client server method includes storing components in a first server, storing a list of the components in a second server, requesting, by an application residing in a client, a component matching particular functioned requirements from the list, negotiating between the first server and the client, and executing the component in response to the negotiation.
Claims36
A method comprising:
- in a network, storing components in a first server;
- storing a list of the components in a second server;
- requesting, by an application residing in a client, a component matching particular functional requirements from the list;
- and
- determining where to execute the requested component according to resource information.
A client server method comprising:
- storing components in a first server;
- storing a list of the components in a second server;
- requesting, by an application residing in a client, a component matching particular functional requirements from the list;
- negotiating between the first server and the client;
- and
- executing the component in response to the negotiation.
A method for automatically using computer software components by an application on a client computer that is connected to a computer network comprising:
- deploying components on a first server;
- registering the components in a second server;
- requesting a particular component by sending a functionality specification of the particular component from the client computer through the application to the second server;
- searching in the second server for register entries that match the functionality specification;
- returning a list of matching components to the application;
- and
- executing a matching component under control of the application.
A computer program product, tangibly stored on a computer-readable medium, comprising instructions operable to cause a programmable processor to:
- in a network, store components in a first server;
- store a list of the components in a second server;
- request, by an application residing in a client, a component from the list;
- and
- execute the component.
A computer program product, tangibly stored on a computer-readable medium, comprising instructions operable to cause a programmable processor to:
- store components in a first server;
- store a list of the components in a second server;
- request, by an application residing in a client, a component from the list;
- negotiate between the first server and the client;
- and
- execute the component in response to the negotiation.
A computer program product, tangibly stored on a computer-readable medium, comprising instructions operable to cause a programmable processor to:
- deploy components on a first server;
- register the components in a second server;
- request a particular component by sending a functionality specification of the particular component from the client computer with the application to the second server;
- search in the second server for register entries that match the functionality specification;
- return a list of matching components to the application;
- and
- execute a matching component under control of the application.
Dependencies are inferred from the claim text.