Component installer permitting interaction among isolated components in accordance with defined rules

• US 7,069,554 B1
• Filed: 01/05/2000
• Issued: 06/27/2006
• Est. Priority Date: 05/06/1998
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Band, Jamie A., Sadler, Andrew P., Stammers, Soren, Patterson, Andrew J.
• Primary Examiner(s): Dam, Tuan
• Assistant Examiner(s): KENDALL, CHUCK O
• Application Number:
  US09/478,624
• Time in Patent Office: 2,365 Days
• Field of Search: 717168-178, 709201-233
• US Class Current: 717/178
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57

Abstract

A programmable computer processing apparatus is connected to a number of servers. Each server stores one or more separate components which, when combined, make up a processing application. Each component specifies any other components which it requires. Computer is arranged to identify a first component needed by an application requested by a user, to fetch the first component from the server storing the component, to fetch any additional components needed by the first component, and to continue fetching components until all of the components required for the application have been fetched. Computer is arranged to install the components in a Java virtual machine using a different classloader for each component and to perform control to permit inter-component interaction and interaction between the components and the resources of computer only in accordance with predefined rules. This prevents unauthorized access by a component to the functionality of another component or computer. Components may be downloaded from servers to take account of upgrades in the components.

Claims

1. A system of connected computer apparatus, comprising a programmable user processing apparatus for use by a user and at least one storage apparatus, the storage apparatus storing data defining separate components of at least one processing application, wherein the user processing apparatus is configured to fetch data defining components of at least one processing application to be used by the user from the storage apparatus, wherein the user processing apparatus is configured to install the components so that the components are isolated from each other by placing the components in separate namespaces, wherein access to each of the separate namespaces is controlled by a loader, wherein the user processing apparatus is configured to permit operational interaction between the components in accordance with defined interaction rules for importing and exporting component functionality between the separate namespaces to enable the application to be used by the user, wherein the user processing apparatus is configured to re-fetch data defining one or more of the components in accordance with defined rules and to use the re-fetched data for the application, and wherein the user processing apparatus is configured to arrange and test the components to verify their authenticity and/or to verify the defined interaction rules.

2. A system according to claim 1, wherein the user processing apparatus is configured to re-fetch data defining one or more of the components in accordance with user instructions and to use the re-fetched data for the application.

3. A system according to claim 1, wherein the user processing apparatus is operable to store data defining at least one of the received components after the application is shut down, and to use the stored data when the application is reused by the user.

4. A system according to claim 3, wherein the user processing apparatus is operable to store and reuse the data in accordance with defined rules.

5. A system according to claim 1, wherein the data defining each component defines any further components which are needed by the component, and wherein the user processing apparatus is configured to receive user instructions defining an application, to determine a first component needed for the application, to fetch the first component and identify any further components required, to fetch any further components required, and to continue identifying and fetching components until all of the components for the required application have been obtained.

6. A system according to claim 5, wherein the user processing apparatus is operable to determine the first component from user instructions.

7. A system according to claim 5, wherein the user processing apparatus is operable to determine the first component from a database of components.

8. A system according to claim 1, wherein the data defining the components includes interaction rules.

9. A system according to claim 8, wherein the rules defined in the data defining components include rules defining functions within a component which will be made available to other components of a specified type.

10. A system according to claim 1, wherein the user processing apparatus is configured to install the components so that the components are isolated from resources of the user processing apparatus, and to permit access by the components to the isolated resources in accordance with defined rules.

11. A system according to claim 10, wherein the user processing apparatus is configured to route each request from a component for access to a resource to a security manager, the security manager being operable to determine whether to permit the access in accordance with pre-stored rules.

12. A system according to claim 1, wherein the user processing apparatus is provided with a virtual machine and is arranged to load each component into the virtual machine.

13. A system according to claim 12, wherein the user processing apparatus is configured to load each component into the virtual machine using a different classloader.

14. A system according to claim 1, wherein the user processing apparatus is configured to provide threads to run each received component, and is further configured to manage the threads such that a component can not change a thread other than one under which it is running.

15. A system according to claim 1, wherein the user processing apparatus is configured to provide threads to run each received component, and is further configured to manage the threads to prevent a component setting the priority of a thread above a predetermined level.

16. A system according to claim 15, wherein the user processing apparatus is configured to set the predetermined level in dependence upon the priority of the threads for running its control functions to ensure that a component cannot override a control function.

17. A system according to claim 1, wherein the user processing apparatus is configured to test received data defining a component to determine whether the component is from a given supplier.

18. A system according to claim 1, wherein the user processing apparatus is configured to test received data defining a component to determine whether the data defining the component has been changed since it was provided by the supplier.

19. A system according to claim 1, wherein the user processing apparatus is operable to use a given component in a plurality of applications.

20. A programmable processing apparatus for use in a system according to claim 1, comprising:

means for downloading data defining a plurality of separate components of a processing application from one or more external apparatus when the programmable processing apparatus is connected to the external apparatus; and

means for installing the received components to enable the application to be used by a user.

21. A storage apparatus for use in a system according to claim 1, comprising:

memory means storing data defining at least one component of a processing application to be transmitted to a programmable user processing apparatus.

22. A system of connected computer apparatus, comprising a programmable user processing apparatus for use by a user and at least one storage apparatus, the storage apparatus storing data defining separate components of at least one processing application, wherein the user processing apparatus is configured to fetch data defining components of a processing application to be used by the user from the storage apparatus, wherein the user processing apparatus is configured to install the components so that the components are isolated from each other by placing the components in separate namespaces wherein access to each of the separate namespaces is controlled by a loader, wherein the user processing apparatus is configured to permit operational interaction between the components in accordance with defined interaction rules for importing and exporting component functionality between the separate namespaces to enable the application to be used by the user, wherein the user processing apparatus is configured to re-fetch data defining one or more of the components in accordance with defined rules and to use the re-fetched data for the application, and wherein the user processing apparatus is configured to arrange and test the components to verify their authenticity and/or to verify the defined interaction rules, the user processing apparatus comprising a downloader configured to download data defining a plurality of separate components of a processing application from one or more external apparatus when the programmable processing apparatus is connected to the external apparatus, and the user processing apparatus comprising an installer configured to install the received components to enable the application to be used by a user.

23. A storage apparatus for use in a system according to claim 22, comprising a memory storing data defining at least one component of a processing application to be transmitted to a programmable user processing apparatus.

24. A programmable processing apparatus, comprising:

a receiver configured to receive data defining a plurality of separate components to make up a processing application; and

a loader configured to install the received components to enable the application to be run, wherein the loader is configured to install the components such that the components are isolated from each other by placing the components in separate namespaces, wherein access to each of the separate namespaces is controlled by the loader, and wherein the loader is configured se as to permit operational interaction between the components in accordance with defined rules for importing and exporting component functionality between the separate namespaces; and

a verifier configured to arrange and test the components to verify their authenticity and/or to verify the defined interaction rules.

25. Apparatus according to claim 24, wherein the loader is configured to permit operational interaction between the components in accordance with rules defined in received data defining the components.

26. Apparatus according to claim 25, wherein the rules defined in the data defining components include rules defining functions within a component which will be made available to other components of a specified type.

27. Apparatus according to claim 24, wherein the loader is configured to install the data so that the components are isolated from resources of the apparatus, and to permit access by the components to the isolated resources in accordance with defined rules.

28. Apparatus according to claim 27, wherein the loader is configured to route each request from a component for access to a resource to a security manager, the security manager being operable to determine whether to permit the access in accordance with pre-stored rules.

29. Apparatus according to claim 24, wherein the loader is arranged to install each component into a virtual machine.

30. Apparatus according to claim 29, wherein the loader is operable to install each component using a different classloader.

31. Apparatus according to claim 24, wherein the receiver is operable to receive data defining a component from a storage medium.

32. Apparatus according to claim 24, wherein the receiver is operable to receive data defining a component transmitted as a signal from an external apparatus.

33. Apparatus according to claim 24, wherein the loader is operable to use a given component in a plurality of applications.

35. A storage device storing instructions for causing a programmable processing apparatus to become configured as an apparatus as claimed in claim 24.

34. A method of operating a programmable processing apparatus, comprising:

receiving data defining a plurality of separate components to make up a processing application;

installing the received components to enable the application to be run, wherein the components are isolated from each other by placing the components in separate namespaces, wherein access to each of the separate namespaces is controlled by a loader, and wherein operational interaction between the components is permitted in accordance with defined rules for importing and exporting component functionality between the separate namespaces; and

arranging and testing the components to verify their authenticity and/or to verify the defined interaction rules.

36. A programmable processing apparatus, comprising:

receiving means for receiving data defining a plurality of separate components to make up a processing application; and

loading means for installing the received components to enable the application to be run, wherein the loading means is configured to install the components such that the components are isolated from each other by placing the components in separate namespaces, wherein access to each of the separate namespaces is controlled by the loading means, and wherein the loading means is configured to install the components so as to permit operational interaction between the components in accordance with defined rules for importing and exporting component functionality between the separate namespaces; and

verifying means for arranging and testing the components to verify their authenticity and/or to verify the defined interaction rules.