MULTI-PROTOCOL ACCESS TO FILES AND DIRECTORIES

• US 20100223443A1
• Filed: 04/30/2010
• Published: 09/02/2010
• Est. Priority Date: 12/18/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Brjazovski, Arkadi, Kumar, Rohan, Steiner, Stefan R., Agarwal, Sameet H., Sreenivas, Mahesh K.
• Granted Patent: US 7,970,747 B2
• Time in Patent Office: Days
• US Class Current: 711/168
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores

Abstract

An operating system is provided. The system includes an agent component to monitor computer activities between one or more single-item access components and one or more set-based access components. A protocol component is employed by the agent component to mitigate data access between the single-item access components and the set-based access components.

Claims

1. A computer-implemented method for controlling memory access in a manner that resolves conflicts between single-item access applications (SIAA) and set-based access applications (SBAA), the method comprising:

defining one or more multiple-protocol access rules that control how access to data items is controlled, denied, and allowed;

maintaining a transaction matrix to control memory interactions, wherein the transaction matrix comprises at least a first operation and a second operation, wherein the first operation in the transaction matrix includes two or more items, and wherein the second operation includes an item dependent on each of the two or more items in the first operation;

monitoring memory locations in view of the multiple-protocol access rules, wherein monitoring memory locations in view of the multiple-protocol access rules comprises;

detecting a first memory access request via a first memory access protocol;

determining that the first memory access request is by an SIAA, wherein an SIAA is a legacy application developed under an operating system framework that allows the SIAA to access only a single data item at a time;

detecting a second memory access request via a second memory access protocol; and

determining that the second memory access request is by an SBAA, wherein an SBAA is an application through which multiple data items, or a set of multiple data items, are concurrently accessible; and

defining one or more multi-access rules that control access to the memory locations and synchronize the SIAA and the SBAA with an agent component in a user mode.

2. The method of claim 1, wherein the two or more items of the first operation includes two or more of:

a Store API transaction modifying an item;

a Data Manipulation Language (DML) modifying an item'"'"'s security;

a Transaction SIAC handle is opened;

a Non-transacted SIAC handle is opened; and

/or

a handle to a child is opened.

3. The method of claim 1, wherein the item in the second operation that is dependent on each of the two or more items in the first operation includes:

a DML Update/Delete/Rename/Replace Item has occurred;

a DML modifying item'"'"'s security has occurred;

a Transacted SIAC open has occurred;

or

a Non-transacted SIAC open has occurred.

4. The method of claim 1, wherein maintaining the transaction matrix and monitoring memory locations is performed by the agent component.

5. The method of claim 1, further comprising:

accessing at least one universal naming component associated with the SIAA or the SBAA.

6. The method of claim 1, further comprising:

determining that the SIAA and SBAA are requesting concurrent access to a data item.

7. The method of claim 6, further comprising:

in response to determining that the SIAA and SBAA are requesting concurrent access to a data item, generating a fault, success flag, or sharing violation while further using the agent component to monitor memory locations.

8. The method of claim 1, wherein detecting a first memory access request includes detecting a request to access a first data item, the first data item being structured as:

a single memory location, an array, a file, a directory, an application, a relational database structure, an object, a class, a method, or a function.

9. The method of claim 1, wherein the second operation is subsequent to the first operation.

10. The method of claim 1, wherein monitoring memory locations includes:

monitoring at least one data item property, the at least one data item property controlling access to the memory.

13. The computer storage medium of claim 1, wherein the item in the second operation that is dependent on each of the two or more items in the first operation includes:

a DML Update/Delete/Rename/Replace Item has occurred;

a DML modifying item'"'"'s security has occurred;

a Transacted SIAC open has occurred;

or

a Non-transacted SIAC open has occurred.

14. The computer storage medium of claim 1, wherein maintaining the transaction matrix and monitoring memory locations is performed by the agent component.

15. The computer storage medium of claim 1, further comprising:

accessing at least one universal naming component associated with the SIAA or the SBAA.

16. The computer storage medium of claim 1, further comprising:

determining that the SIAA and SBAA are requesting concurrent access to a data item.

17. The computer storage medium of claim 6, further comprising:

in response to determining that the SIAA and SBAA are requesting concurrent access to a data item, generating a fault, success flag, or sharing violation while further using the agent component to monitor memory locations.

18. The computer storage medium of claim 1, wherein detecting a first memory access request includes detecting a request to access a first data item, the first data item being structured as:

a single memory location, an array, a file, a directory, an application, a relational database structure, an object, a class, a method, or a function.

19. The computer storage medium of claim 1, wherein the second operation is subsequent to the first operation.

11. A computer storage medium having stored thereon computer executable instructions that, when executed within a computing environment, cause a computing system to perform a method for controlling memory access in a manner that resolves conflicts between single-item access applications (SIAA) and set-based access applications (SBAA), the computer executable instructions including instructions causing the computing system to:

define one or more multiple-protocol access rules that control how access to data items is controlled, denied, and allowed;

maintain a transaction matrix to control memory interactions, wherein the transaction matrix comprises at least a first operation and a second operation, wherein the first operation in the transaction matrix includes two or more items, and wherein the second operation includes an item dependent on each of the two or more items in the first operation;

monitor memory locations in view of the multiple-protocol access rules, wherein monitoring memory locations in view of the multiple-protocol access rules comprises;

detecting a first memory access request via a first memory access protocol;

determining that the first memory access request is by an SIAA, wherein an SIAA is a legacy application developed under an operating system framework that allows the SIAA to access only a single data item at a time;

detecting a second memory access request via a second memory access protocol; and

determining that the second memory access request is by an SBAA, wherein an SBAA is an application through which multiple data items, or a set of multiple data items, are concurrently accessible; and

define one or more multi-access rules that control access to the memory locations and synchronize the SIAA and the SBAA with an agent component in a user mode.

12. The computer storage medium of claim 11, wherein the two or more items of the first operation includes two or more of:

a Store API transaction modifying an item;

a Data Manipulation Language (DML) modifying an item'"'"'s security;

a Transaction SIAC handle is opened;

a Non-transacted SIAC handle is opened; and

/or

a handle to a child is opened.

20. A computing system for controlling memory access in a manner that resolves conflicts between single-item access applications (SIAA) and set-based access applications (SBAA), the system comprising:

one or more processors;

one or more computer storage media having stored thereon computer executable instructions that, when executed by the one or more processors, cause the computing system to;

define one or more multiple-protocol access rules that control how access to data items is controlled, denied, and allowed;

maintain a transaction matrix to control memory interactions, wherein the transaction matrix comprises at least a first operation and a second operation, wherein the first operation in the transaction matrix includes two or more items, and wherein the second operation includes an item dependent on each of the two or more items in the first operation;

monitor memory locations in view of the multiple-protocol access rules, wherein monitoring memory locations in view of the multiple-protocol access rules comprises;

detecting a first memory access request via a first memory access protocol;

determining that the first memory access request is by an SIAA, wherein an SIAA is a legacy application developed under an operating system framework that allows the SIAA to access only a single data item at a time;

detecting a second memory access request via a second memory access protocol; and

determining that the second memory access request is by an SBAA, wherein an SBAA is an application through which multiple data items, or a set of multiple data items, are concurrently accessible; and

define one or more multi-access rules that control access to the memory locations and synchronize the SIAA and the SBAA with an agent component in a user mode.