PRE-CALCULATION AND CACHING OF DEPENDENCIES

• US 20110016477A1
• Filed: 07/14/2009
• Published: 01/20/2011
• Est. Priority Date: 07/14/2009
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Subramanyam, Karthik, Paulin, Alan P., Schechter, Greg D.
• Application Number:
  US12/503,037
• Publication Number:
  US 20110016477A1
• Time in Patent Office: Days
• US Class Current: 719/330
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading

Abstract

Dependencies among components may be pre-calculated, validated and cached. The cached dependencies may then be used in an execution environment to inject dependencies into the component. In one example, components for a web application are submitted to the operator of the application. Dependencies among the components may be pre-calculated, and the pre-calculated dependencies may be stored in a catalog. When a client accesses the web application, the components may be downloaded to the client along with the catalog. The client may provide a virtual machine or other execution environment under which the components execute. The execution environment may provide a dependency injection feature that connects components together at runtime based on the pre-calculated dependencies in the catalog.

Claims

1. A method of supporting interaction between software components, the method comprising:

using a processor to perform acts comprising;

receiving a first component;

identifying, in said first component, a contract to be imported into said first component from outside of said first component;

determining that a second component exists that exports said contract;

creating a catalog that comprises an indication that, to provide functionality under said contract to said first component, said second component is to be connected to said first component;

receiving, from a client, a request to invoke an application that comprises said first component; and

transmitting, to said client, said first component and said catalog.

2. The method of claim 1, wherein said catalog comprises:

data that identifies said first component as an importer of said contract; and

data that identifies said second component as an exporter of said contract.

3. The method of claim 1, wherein said acts further comprise:

determining there is not a type mismatch between said first component and said second component.

4. The method of claim 1, wherein said acts further comprise:

determining, based on an access control rule, that said second component is allowed to be used by said first component.

5. The method of claim 1, wherein said acts further comprise:

including said first component in a Dynamic Link Library (DLL) file that includes one or more other components;

wherein said transmitting of said first component comprises transmitting said DLL file to said client.

6. The method of claim 5, wherein said acts further comprise:

creating a compressed file that comprises said DLL file and one or more other DLL files;

wherein said transmitting of said DLL file comprises transmitting said compressed file to said client.

7. The method of claim 1, wherein said contract is identified by a string, wherein said first component comprises an import instruction that includes said string, and wherein said second component comprises an export instruction that includes said string.

8. The method of claim 1, wherein said first component comprises a first property name that is associated with a first object to be imported under said contract, wherein said second component comprises a second property name that is associated with a second object to be exported under said contract, and wherein said catalog lists said first property name with a record of said first object and lists said second property name with a record of said second object.

9. The method of claim 8, wherein said first object is of a type, wherein said second object is of said type, and wherein said catalog lists said type in said catalog'"'"'s records of said first object and said second object.

10. The method of claim 1, wherein said first component comprises a plug-in for a web application, and wherein said client requests to use said web application.

11. The method of claim 10, wherein said web application is provided by a first party, and wherein said receiving of said first component comprises:

receiving said first component from a second party that is different from said first party.

12. One or more computer-readable storage media that store executable instructions to allow components to interoperate, wherein said instructions, when executed on a computer, cause the computer to perform acts comprising:

receiving, from a machine through a communication network, a catalog that comprises an indication that;

(a) a first component imports a contract, and (b) a second component exports said contract;

receiving, from said machine through said communication network, a first file that comprises said first component;

loading said first component into an execution environment;

determining, based on said catalog, that said first component is dependent on said second component;

receiving a request for action that is to be performed by said first component but that does not use functionality that said first component imports from said second component under said contract; and

allowing said first component to execute without said second component being loaded into said execution environment.

13. The one or more computer-readable storage media of claim 12, wherein said first file is a Dynamic Link Library (DLL) file that comprises said first component and one or more other components.

14. The one or more computer-readable storage media of claim 13, wherein first file is a compressed file that comprises said DLL file and one or more other DLL files.

15. The one or more computer-readable storage media of claim 12, wherein said acts further comprise:

determining that a set of access control rules permit said second component to be used with said first component.

16. The one or more computer-readable storage media of claim 12, wherein said execution environment allows said first component to execute when said second component is not present on a machine at which said execution environment operates.

17. The one or more computer-readable storage media of claim 12, wherein said acts further comprise:

making a request, to a server, to operate an application that is provided by said server;

wherein said request is made by a client to a server, wherein said server provides an application that executes on said client, and wherein said first component is a plug-in for said application.

18. A system for controlling interoperation among executable components, the system comprising:

a processor;

a data remembrance component;

a dependency calculation component that executes on said processor and that is stored in said data remembrance component, the system receiving a first component that specifies a contract to be imported and a second component that specifies that said second component exports said contract, the dependency calculation component determining, based on an access rule, that said second component is not be used with said first component, said dependency calculation component generating a catalog that identifies said first component as an importer of said contract and that further identifies said second component as an exporter of said contract, said catalog indicating that said second component is not to be used to export said contract to said first component; and

a communications mechanism through which said first component and said catalog are communicated to a client that provides an execution environment on which said first component and said second component execute.

19. The system of claim 18, wherein said first component is sent to said client in a Dynamic Link Library (DLL) file that includes one or more other components that are in an intermediate language that is executable on a virtual machine provided by said execution environment.

20. The system of claim 18, wherein said dependency calculation component identifies a third component that export said contract and includes, in said catalog, an indication that said third component is to be used to provided, to said first component, functionality associated with said contract.