Resource usage conflict identifier

• US 7,673,051 B2
• Filed: 07/26/2005
• Issued: 03/02/2010
• Est. Priority Date: 07/26/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kaplan, Jesse D., Wadsworth, Brandon Scott, Grunkemeyer, Brian M.
• Primary Examiner(s): NGUYEN, PHUOC H
• Application Number:
  US11/189,284
• Publication Number:
  US 20070028245A1
• Time in Patent Office: 1,680 Days
• Field of Search: 709/226, 717/131
• US Class Current: 709/226
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

The exposure and usage of one or more particular physical and logical resources by methods within an isolation boundary may be annotated so as to preempt resource usage conflicts. Further described are tools, contracts, and collaborative processes for at least identifying potential resource usage conflicts. More particularly, the example tools, contracts, and collaborative processes may be used to annotate at least one of exposure and consumption of one or more particular physical and logical resources by methods within an isolation boundary.

Claims

1. A process, comprising:

receiving an identity of methods that expose a resource outside of a given isolation boundary that is an application domain within a managed execution environment;

evaluating a scope of resource consumption and exposure by the identified methods in the isolation boundary;

applying a contract to the identified methods for annotating; and

submitting the contracted methods for annotating based on the evaluated scope of resource method, the process being performed by a computing device.

2. A process according to claim 1, wherein the receiving includes receiving the identity of the method from an analysis tool.

3. A process according to claim 1, wherein the evaluating includes verifying that the identified methods are to expose the resource to other identified methods within the isolation boundary.

4. A process according to claim 1, wherein the evaluating includes narrowing the scope of the resource exposure by the identified methods within the isolation boundary.

5. A process according to claim 1, wherein the applying a contract includes applying the identified methods with a contract to indicate the evaluated scope of resource exposure and consumption.

6. A process according to claim 1, wherein the submitting includes submitting the methods to a static analysis tool.

7. A process according to claim 1, wherein the process is repeated until no further unmarked methods that expose the resource are identified.

8. At least one computer-readable medium having executable instructions that, when read, cause one or more processors to:

identify a first call site to expose a resource that is outside an isolation boundary that is an application domain within a managed execution environment;

identify at least two methods that call a method that exposes a resource;

apply a contract to the at least two methods with a corresponding scope of consumption and scope of exposure; and

annotate changes of a scope of consumption and exposure for the resource relative to the isolation boundary.

9. At least one computer-readable medium according to claim 8, wherein the first call site implements an unmanaged method call.

10. At least one computer-readable medium according to claim 8, wherein the resource is shared state.

11. At least one computer-readable medium according to claim 8, wherein the potential resource usage conflicts pertain to at least one of a physical resource or a logical resource.

12. At least one computer-readable medium according to claim 8, wherein the one or more instructions to identify the potential resource usage conflicts cause the one or more processors to compare resource exposure and consumption contracts in the at least two methods.

13. At least one computer-readable medium according to claim 8, wherein the one or more instructions to apply a contract to the at least one method cause the one or more processors to attach at least one process pertaining to usage of the resource and at least one process pertaining to narrowing a scope of the method within the isolation boundary.

14. At least one computer-readable medium according to claim 8, wherein the one or more instructions to apply a contract to the at least one method within the isolation boundary further cause the one or more processors to avail the at least one method to a contributing developer of the at least one method.

15. A system, comprising:

a processor;

an identifier operable to identify at least one method to expose a resource related to a given isolation boundary that is an application domain within a managed execution environment;

a comparator operable to compare the identified methods operable to use the resource with regard to consumption of the resource;

a contractor operable to apply a contract to those of the compared methods that may conflict when attempting to use the resource; and

a manager operable to gauge whether the contracted methods are to be re-submitted to the system wherein operations of the identifier, the comparator, the contractor, and the manager are performed by the processor.

16. A system according to claim 15, wherein the identifier is to identify methods that access shared state.

17. A system according to claim 15, wherein the contractor is to apply a contract by appending an explanation of resource consumption to one of the methods and an explanation of how the resource is be exposed to further methods.

18. A system according to claim 15, wherein the manager is to receive those of the contracted methods having had a scope thereof reduced from an external source that may avoid a resource conflict and/or reduce exposure of the resource to one or methods in a particular isolation boundary.