Locking semantics for a storage system based on file types

• US 20080243846A1
• Filed: 04/02/2007
• Published: 10/02/2008
• Est. Priority Date: 04/02/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Rasmussen, David J.
• Granted Patent: US 8,433,693 B2
• Time in Patent Office: Days
• US Class Current: 707/8
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files

Abstract

Techniques for implementing locking semantics for a storage system based on file types are described. An apparatus or system may include a database to store multiple data files, and a cache manager to manage the data files, the cache manager having a client lock manager to receive a request to modify a data file, determine a file type for the data file, access a set of locking semantics based on the file type, and determine whether the data file can be modified based on the locking semantics. Other embodiments are described and claimed.

Claims

1. A method, comprising:

receiving a request to modify a data file by an application program at a client;

determining a file type for the data file;

accessing a set of file access rules based on the file type; and

determining whether the application program can modify the data file based on the file access rules.

2. The method of claim 1, comprising:

determining the file type is an immutable file type; and

granting permission to the application program to modify the file by the client.

3. The method of claim 1, comprising:

determining the file type is a locking required file type;

determining whether a network connection to a locking server is available; and

denying permission to modify the file when the network connection is not available.

4. The method of claim 1, comprising:

determining the file type is a locking required file type;

determining whether a network connection to a locking server is available;

sending a lock request to lock the data file to the locking server when the network connection is available; and

granting permission to modify the file when the lock request is granted by the locking server.

5. The method of claim 1, comprising:

determining the file type is a locking required file type;

determining whether a network connection to a locking server is available;

sending a lock request to lock the data file to the locking server when the network connection is available; and

denying permission to modify the file when the lock request is denied by the locking server.

6. The method of claim 1, comprising:

determining the file type is a locking preferred file type;

determining whether a network connection to a locking server is available; and

granting permission to modify the file when the network connection is not available.

7. The method of claim 1, comprising:

determining the file type is a locking preferred file type;

determining whether a network connection to a locking server is available;

sending a lock request to lock the data file to the locking server when the network connection is available; and

granting permission to modify the file when the lock request is granted by the locking server.

8. The method of claim 1, comprising:

determining the file type is a locking preferred file type;

determining whether a network connection to a locking server is available;

sending a lock request to lock the data file to the locking server when the network connection is available; and

denying permission to modify the file when the lock request is denied by the locking server.

9. An article comprising a storage medium containing instructions that if executed enable a system to:

receive a request to modify a data file by an application program;

determine a file type for the data file;

access a set of locking semantics based on the file type; and

determine whether the application program can modify the data file based on the locking semantics.

10. The article of claim 9, further comprising instructions that if executed enable the system to:

determine the file type is an immutable file type; and

grant permission to the application program to modify the file.

11. The article of claim 9, further comprising instructions that if executed enable the system to:

determine the file type is a locking required or a locking preferred file type;

determine a network connection to a locking server is available;

request locking instructions from the locking server; and

provide a response to the request to modify based on the locking instructions.

12. The article of claim 9, further comprising instructions that if executed enable the system to:

determine the file type is a locking required file type;

determine whether a network connection to a locking server is available; and

deny permission to modify the file when the network connection is not available.

13. The article of claim 9, further comprising instructions that if executed enable the system to:

determine the file type is a locking required file type;

determining whether a network connection to a locking server is available;

sending a lock request to lock the data file to the locking server when the network connection is available;

granting permission to modify the file when the lock request is granted by the locking server; and

denying permission to modify the file when the lock request is denied by the locking server.

14. The article of claim 9, further comprising instructions that if executed enable the system to:

determine the file type is a locking preferred file type;

determine whether a network connection to a locking server is available; and

grant permission to modify the file when the network connection is not available.

15. The article of claim 9, further comprising instructions that if executed enable the system to

determine the file type is a locking preferred file type;

determine whether a network connection to a locking server is available;

send a lock request to lock the data file to the locking server when the network connection is available;

grant permission to modify the file when the lock request is granted by the locking server; and

deny permission to modify the file when the lock request is denied by the locking server.

16. An apparatus comprising:

a database to store multiple data files; and

a cache manager to manage the data files, the cache manager having a client lock manager to receive a request to modify a data file, determine a file type for the data file, access a set of locking semantics based on the file type, and determine whether the data file can be modified based on the locking semantics.

17. The apparatus of claim 16, the client lock manager to determine the file type is an immutable file type and grant permission to modify the file.

18. The apparatus of claim 16, comprising a transceiver, the client lock manager to determine the file type is a locking required or a locking preferred file type, establish a network connection to a locking server using the transceiver, request locking instructions from the locking server over the network connection, and provide a response to the request to modify based on the locking instructions.

19. The apparatus of claim 16, comprising a transceiver, the client lock manager to determine the file type is a locking required file type, determine a network connection to a locking server is not available, and deny permission to modify the file.

20. The apparatus of claim 16, comprising a transceiver, the client lock manager to determine the file type is a locking preferred file type, determine a network connection to a locking server is not available, and grant permission to modify the file.