Naming service database updating technique

• US 5,408,619 A
• Filed: 06/17/1993
• Issued: 04/18/1995
• Est. Priority Date: 09/08/1987
• Status: Expired due to Term

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Digital Equipment Corporation (HP Inc.)
• Inventors: Oran, David R.
• Primary Examiner(s): Coleman, Eric
• Application Number:
  US08/079,701
• Time in Patent Office: 670 Days
• Field of Search: 395/275, 395/325, 395/600
• US Class Current: 1/1
• CPC Class Codes: G06F 13/387 for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: H04L 69/00 Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass networks security protocols H04L9/40; wireless communication networks H04W

Abstract

A naming service for use in a network which includes a plurality of client nodes and server nodes interconnected by a communications link. Each of the client nodes includes a clerk for transmitting service request messages to initiate selected operations. At least one of said server nodes includes a nameserver which includes a transaction agent, a database which contains a plurality of entries each containing attributes relating to an object, such as the location of related entries in any other nameservers, an update transfer portion and a control portion. The transaction agent receives service request messages from the clerk. In response to a service request message received by the transaction agent from the client node'"'"'s clerk, the control module enables the update transfer section to transfer database updates over said communications link.

Claims

1. A naming service for use in a plurality of client nodes and a plurality of server nodes interconnected by a communications link, said naming service comprising:

A. a database of entries each containing information needed for responding to name service requests from said client nodes;

B. a clerk means in each of said client nodes for transmitting service request messages to initiate selected operations, said service request messages including database update request messages for causing entries of said database to be updated;

C. a name server means in each of at least two of said server nodes, each of said name server means including;

i. transaction agent means for receiving said service request messages from said clerk means;

ii. database means containing at least a portion but not all of said database entries;

iii. update means for updating said entries in response to said database update request messages if said database means contains the entries to be updated;

iv. update transfer means connected to said communications link for transferring database update requests and database updates over said communications link from said name server means in one server node to other server nodes containing name server means, regardless of whether the database means in the one server node contains the entries to be updated; and

v. control means connected to said transaction agent means, said database means, and said update transfer means for enabling said update transfer means and said database means to engage in an update operation cooperatively with another server node containing name server means in response to a database update request message received by said transaction agent means.

2. A naming service method for use with client nodes and server nodes interconnected by a communications link, said naming service method comprising:

A. storing in a database means entries containing information needed for responding to name service request messages from said client nodes;

B. transmitting service request messages from said client nodes to initiate selected operations, said service request messages including database update request messages for causing entries of said database means to be updated;

C. in each of two of said server nodes;

i. receiving some of said service request messages through a transaction agent means at one of said server nodes;

ii. storing in said database means at said one server node a portion but not all of said database entries;

iii. updating at least some of said entries in response to said database update request messages if said one server node contains the entries to be updated;

iv. transferring said database update request messages and database updates over said communications link from said one server node to another server node, regardless of whether said one server node contains entries to be updated; and

v. engaging in an update operation cooperatively with said other server node in response to said database update request message.

3. The method of claim 2 wherein said database means includes entries for a directory residing at more than one location in a network, and the directory has a network address for each location at which the directory resides.

4. The method of claim 3 wherein each of said entries for a directory is replicated at multiple server nodes.

5. The method of claim 3 wherein each of said entries for a directory includes an attribute specifying the degree of effort required to maintain the directory'"'"'s replicas up to date.

6. The method of claim 3 wherein each of said entries for a directory includes attributes identifying the relationship, in a tree structure, of that directory with other directories.

7. The method of claim 3 wherein each of said entries for a directory includes attributes identifying the locations of the directory in the network.

8. The method of claim 7 wherein

when a directory in said database means on a server node is updated by addition or deletion of an object, entries relating to the directory in database means in other of said server nodes are updated using attributes identifying other server nodes whose database means contain entries for the object.

9. The method of claim 7 wherein

if one of said server nodes is unable to accept an update service request for an entry for a directory, the server node which initiated the update service request will retry as specified in a convergence attribute for said entry and the relationship between an attribute specifying the data of the last update and an attribute identifying how up-to-date entries for the directory are to be.