초록 ▼

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 sto

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.

대표청구항 ▼

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

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.