System and method for providing opportunistic file access in a network environment

• US 5,628,005 A
• Filed: 06/07/1995
• Issued: 05/06/1997
• Est. Priority Date: 06/07/1995
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hurvig, Hans
• Primary Examiner(s): Kulik, Paul V.
• Application Number:
  US08/478,454
• Time in Patent Office: 699 Days
• Field of Search: 395/600, 395/200.09, 395/200.12, 395/200.14, 395/427, 395/440, 395/445, 395/448, 395/462, 395/468, 395/726, 395/650
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0813 with a network or matrix configuration
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 2212/311 In host system
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database

Abstract

A file allocation and management system for a multi-user network environment is disclosed. At least one server and two or more clients are disposed along the network in communicating via a request/response transfer protocol. Files directed for shared usage among the clients along the network are stored at the server. Each client is adapted to communicate with the server through a plurality of identifier sockets, wherein a first identifier socket is configured for bi-directional communication and a second identifier socket is configured for uni-directional communications initiated by the server. Files normally stored at the server, under appropriate circumstances may be temporarily stored in an internal cache or other memory at each client location, when the file is in use.

Claims

1. A method for allocating and managing files in a multi-user network environment of the type having at least one server with a file directed for shared usage, and a plurality of clients interconnected with the server through a network link, each client having at least two identifier sockets, wherein a first identifier socket is configured for bi-directional communication between the client and the server and a second identifier socket is configured for unidirectional communications initiated by the server, the method comprising the steps of:

transmitting by the client through said first identifier socket a request to the server for the file;

determining by the server whether the file is available to the client for opportunistic access;

transmitting by the server the file to the requesting client through the first identifier socket;

notifying the client by the server whether the client has an opportunistic lock on the file or whether the file must be maintained at the server; and

sending by the server a message to the client through the second identifier socket that the client must relinquish the opportunistic access to the file when the server determines that opportunistic access is no longer available.

2. The method of claim 1 further comprising the steps of:

transmitting by the client through the first identifier socket a notification request to the server that the client is relinquishing access to the file;

determining by the server whether the relinquished file is available for opportunistic access by a second client accessing the file; and

notifying the second client by the server through the second identifier socket of the second client that the file is available for opportunistic access.

3. The method of claim 1 further comprising the step of relinquishing by the client the opportunistic lock on the file by transmitting to the server any portions of the file that have been modified by the client.

4. The method of claim 1 wherein the step of determining whether the file is available to the client for opportunistic access includes the step of referencing an opportunistic file table maintained by the server comprising information related to which clients have open access to the file and whether the file is open for read-only or read-write access.

5. The method of claim 2 wherein the step of determining whether the file is available to a second client for opportunistic access includes the step of referencing an opportunistic file table maintained by the server comprising information related to which clients have open access to the file and whether the file is open for read-only or read-write access.

6. A file allocation and management system for a multi-user network environment of the type having at least one server which maintains a file for shared usage at the server and two or more clients that communicate in a request/response protocol, the system comprising:

a plurality of identifier sockets at each client, wherein a first identifier socket is configured for bi-directional communication with the server, the bi-directional communication being initiated by a request from the client, and a second identifier socket is configured to receive unidirectional communications initiated by the server;

a cache memory at each client, the cache memory being in communication with the server through the first identifier socket, wherein the file is transported between the cache memory and server through the first identifier socket; and

a cache controller for controlling the file transport and storage within the cache memory, both the cache controller and the server being disposed to communicate so as to controllably transport the file between the cache memory and the server, wherein the file is transported between the cache memory and the server in dependance upon the number of clients having open access to the file, and whether the file is open for read-only or read-write access.

7. The file allocation and management system of claim 6 wherein the second identifier socket of the clients are configured to receive communication from the server related to whether the clients are permitted opportunistic access to the file.

8. The file allocation and management system of claim 7 wherein said communication from the server includes a request by the server for a client to release an opportunistic lock on the file.

9. The file allocation and management system of claim 8 wherein said client is configured to release the opportunistic lock on the file by flushing its cache and transmitting to the server any portions of the file that have been modified by the client.

10. The file allocation and management system of claim 6 wherein said server maintains an opportunistic file table comprising information related to which clients have said open access to the file and whether the file is open for read-only or read-write access.

11. The file allocation and management system of claim 10 wherein said server determines if opportunistic access to the file is possible by one or more clients by referencing said opportunistic file table when a client relinquishes access to the file.

12. A client network driver usable in a multi-user network environment of the type having at least one server which maintains a file for shared usage at the server and two or more clients that communicate in a request/response protocol over a network link, the client network driver comprising:

a client network interface operable to receive data packets comprising the file from the network link through a first identifier socket which is configured for bi-directional communication with the server, the bi-directional communication being initiated by a request from the client, and

a controller operable to store and maintain the file received by the client network interface through the first identifier socket on a local storage device of the client, and further operable to flush the file from the local storage device in response to a unidirectional communication initiated by the server through a second identifier socket directing the client to release an opportunistic lock on the file.