CA1312385C - Naming service for networked digital data processing system - Google Patents
Naming service for networked digital data processing systemInfo
- Publication number
- CA1312385C CA1312385C CA000576625A CA576625A CA1312385C CA 1312385 C CA1312385 C CA 1312385C CA 000576625 A CA000576625 A CA 000576625A CA 576625 A CA576625 A CA 576625A CA 1312385 C CA1312385 C CA 1312385C
- Authority
- CA
- Canada
- Prior art keywords
- service
- database
- server
- nodes
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/382—Information transfer, e.g. on bus using universal interface adapter
- G06F13/387—Information transfer, e.g. on bus using universal interface adapter for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
Abstract
ABSTRACT OF THE DISCLOSURE
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,
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,
Description
1 3 1 2~
1~65V
NAMING SERVICE FOR NETWORKED
DIGITAL DATA PROCESSING SYSTE~
BACKG~OUND OF_THE INVENTION
1._ Field of the Invent _n The invention relates generally to the field of digital data processing systems and more specifically to networks for use in connection wi-th distributed systems.
1~65V
NAMING SERVICE FOR NETWORKED
DIGITAL DATA PROCESSING SYSTE~
BACKG~OUND OF_THE INVENTION
1._ Field of the Invent _n The invention relates generally to the field of digital data processing systems and more specifically to networks for use in connection wi-th distributed systems.
2. Description of the .Prior Art A digital data processing system, or computer, typically includes a processor, associated memory and input/output units enabling a user to load programs and data into the computer and obtain processed data therefrom. In the past, computers were expensive, and so to be cost effective had to support a number of users. More recently, however, the cost of computers, particularly the processors and memories, has decreased substantially, and so it is relatively cost effective to provide a computer to one or at most only a few users.
A benefit of providing only a single computer for a large number of users was that the users could easily share information. Thus, for example, if all persons working in a bookkeeping or accounting department use a single common computer, they may maintain common accounting and bookkeeping databases up to date, and when necessary accounting reports may be generated from those databases. However, if they use separate computers, the data is stored in separate databases, on each computer, and so generating accounting reports would be more difficult.
As a result, networks were developed to provide a distributed computer system, that is, a system which permits diverse computers to communicate and transfer data among them. In addition, the networks allow the :
:: :
~312385 sharing of expensive input/output devices, such as printers and mass storage devices, and input/output devices which may be rarely used, such as links to the public telecommunications network. In a network, each computer is a node which communicates with other nodes over one or several wires. In addition, nodes may be provided which store and manage databases or other data files on mass storage devices, or which manage printers or links to the public telecommunications network.
A problem arises with networks, however, since resources used in the network, such as programs and data files, the input/output devices and so forth, are typically stored in, or connected to, only some of the nodes. If clients on other nodes need to use such resources, they must be able to find them. In the past, each client node had to maintain a file identifying the location, within the network, of all resources which were available to the client. With a large network with many resources, this arrangement required substantial amounts of memory at each client node devoted only to the storage of such location information. In addition, maintaining location information in the diverse client nodes in an updated and current condition was difficult and required processing by the client node and transfers over the network which could otherwise be used for more useful information processing purposes.
More recently, naming services have been developed which maintained the identification of the locations of the resources available in a network. Naming services maintain the location information in only a few locations in the network, and provide the information to a client node on reguest. In addition, the naming services update the location information over the network without client node processing.
~312385 SUMMARY OF_ THE INVENTION
The invention provides a new and improved naming service for use in a network.
In brief summary, the present invention provides a naming service for use ln 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 fox responding -to name service requests from said client nodes; B. a clerk means in each of said client nodes for transmittin~ service request messages to initiate selected operations, said service request messages including database update request messages for causing entries of said database ~o be updated; C. a name server means in each of at least two of said server nodes, 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 databaæe entries; iii. update means for updating said entries in response to said database ~; update request messages; iv. update transfer means connected to said communications link ior transferring database update requests and database updates over said communications link from said name server means to other server nodes containing name server means;
and v. control means connected to said transaction agent means, : sald data base means, and said update transfer means for enabling : said update transfer means and said data base means to engage in an update operation cooperatively with another server node containing name server means in response to a database update ~ ~B
60~12-1825 request message received by said transaction agent means.
According to another aspect, the invention provides a method for use by a name service distributed between at least two server nodes in a system having a plurality of clien~ nodes and a plurallty of server nodes interconnected by a communications link for updating a plurality of name service database entries, each of each said database entries containing attributes associated with an object, said database entries being distributed among said server nodes con~aining said name service, said method comprising the steps of: a. receiving from a cllent node at one of said ; server nodes containing said name service a request for service which includes updating said database, b. checking whether said one of said server nodes is an appropriate node to respond to said request for service, c. passing said request for service to an appropria~e service node if said one of said server nodes is not an appropriate node to respond to said request for service, and d.
performing said database update reguest including passing corresponding database updates to another said server node containing said name service.
BRIEF DESCRIPTION_OF THE DRAWINGS
This invention is pointed out with particularity in the appended claims. The above and further advantages of this invention may be better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:
Fig. 1 is a general block diagram of a distributed 3a 60~l2-læ2s digital data processing system con~tructed in accordance with the invention;
Fig. 2 is another block diagram useful in understanding the invention.
DETAILED DESCRIPTION OF AN ILLUSTRATIVE FMBODIMENT
Fig. 1 is a general block diagram of a distributed digital data processing system constructed in accordance with the invention. With reference to Fig. 1, the system includes a plurality of nodes, including server nodes lOA throuyh 10N
(generally identified by reference 3b 4 60~12-1~25 numeral 10) and a plurality oE cllent nodes llA through llN
(generally identifled by reference numeral 11) lnterconnected by a communlcatlons llnk 12. The server nodes 10 provide a number of servlces to cllent no~es 11. The cllent nodes 11 are used by users to perform or lnltlate data processlng. Examples of ser-vlces provlded by server nodes 11 lnclude prlntlng and telecom-munlcatlons services, data processlng, mass storage backup of data whlch is processe~ by the cllent nodes 11 or by a server node 10, and common database control for client nodes 11, allowlng a plur-allty of cllent nodes to acce~s a common database. It wlll beappreclated that not all server nodes provlde all of such servlces to the cllent nodes 10; ln some cases, one or only a few server nodes 10 may provlde a partlcular servlce to the cllent nodes 11.
In addltlon, some of the server nodes 10 may provlde multlple ser-vices to the cllent nodes 11.
At least one server node 10 ln the system provldes a naming servlce 13. In brlef, a namlng service provides from a slngle locatlon, namely the server node contalnlng the namlng servlce, the locatlon of any ob~ect in server nodes 10 and client nodes 11 whlch ~ay be accessed by a client node 11. An object is typically a flle, for example, a program or a data flle, whlch ls ldentlfled by a name, or a directory, whlch may contain a file or other directory, which ls also identified by a name, or any other addressable resource in the system. A client node 11 whlch re-qulres access to an ob~ect, provldes the namlng servlce 13 wlth the name of the ob~ect, and the namlng servlce identlfles the client node 11 or server node 10 which controls the ob~ect and through whlch the ob~ect can be accessed. Dependlng on the number of ob~ects, client nodes 11 and server nodes lo, the naming service may be divided among several server nodes lo.
In particular, the naming service provides a database having a plurality of entries each associated with an object. Each server node 10 which serves to maintain portions of the naming service contains part, but not necessarily all, of a copy of the database; that is, portions of the database may be maintained on several of the server nodes 10 which form part of the database. Parts of the database may be replicated among the various server nodes 10.
The database entries contain attributes for each of the objects. In one embodiment, attributes include such information as the object identifier, an update timestamp, access rights to the object, and the network address of the object. If the object is a directory, the directory may reside at more than one location, and if so the directory will have a network address for each ~ ~ c ~
~ ca~t-~. In addition, if an object is a directory, its entry may be replicated in several of the server nodes 10, and attributes associated with each directory entry identify the locations of the directory in the network, how up to date each location is, and a convergence attribute which specifies the degree of effort required to be expended to maintain the directory's replicas up to date. An entry for a directory also identifies its relationship with other directories, in a system which maintains tree-structured directories.
Fig. 2 depicts a block diagram of modules in the naming service in the system depicted in Fig. 1. The naming service includes a clerk 20, which actually resides in all of the client hodes 11, and one or more nameservers generally identified by reference numeral 30, with each nameserver 30 residing in a server node - 6 - 13t2385 10. The clerk 20 provides the client interface to enable a client node 11 to communicate with the nameservers 30 in the various server nodes 10.
The nameservers 30 are all similar and so one nameserver, namely nameserver 3OA, will be described in detail. Nameserver 30A includes a transaction agent module 31A which communicates with the clerks 20, an update sender module 32A and an update receiver module 33A, which respectively communicate to other nameservers 30 changes to a database 34A and receive from other nameservers 30 and enter changes for the database 34.
Database 34 is the portion of the name service database resident on the particular nameserver. A control module 35A controls accesses to the database, and the operation of the transaction agent 31A, update sender 32A and update receiver 33A.
More specifically, periodically the transaction agent 31 in the nameserver 30 in each of the server nodes 10 which forms part of the naming service broadcasts over the communications iink 12 a solicitation advertising message, using a SOL ADV PROT
solicitation advertising protocol, notifying the clerks 20 in all of the client nodes 11 of their existence.
When the client node 11 requires service from a nameserver, it transmits, usi.ng a CLK SERV PROT clerk server protocol, a service request. A client node 11 may require service for several reasons. For example, the client node may need to access an object or obtain information about an object, such as the various subdirectories of a directory. Alternatively, a client node 11 may need to create an object, particularly a directory or a file, delete an object, or modify various attributes, such as access rights, with respect to an object. In addition, a client node may require a directory to be backed up. To initiate these services, the client node 11, through its clerk, transmits a service request to a transaction agent 31 about which it previously learned from the transaction agent's prior solicitation advertising message.
The transaction agent 31 receives the service request from the clerk and communicates with its control module to determine whether the nameserver 30 is the proper one to service the request. The control module 35 must first determine, from the records in data base 34, whether it maintains entries relating to the object, if it is to be deleted, backed up or accessed, or if it maintains the directory in which the object is to be created if a new object is to be created. If it does, it may accept the service request. If it does not, the control module 35 enables the transaction agent 31 to either refuse the service request or to transmit the service request to another nameserver 30, also using the CLK SERV PROT in communication with the transaction agent 31 of the other nameserver 30.
If the service request can be performed by a nameserver 30, the control module 35 enables operations which depend on the particular service request. For example, if the service request requires creation of an object, the control module 35 creates a new entry in the database 34 for the object and enters the various attributes. If an object is created in a directory, the control module at some point enables transaction agent 31 to update entries relating to the directory in databases 34 in other nameservers 30 to reflect creation of the object in the directory using a DIR MAIN PROT
directory maintenance protocol. The transaction agent 31 uses the attributes in the object's entry in the database 34 identifying other nameservers 30 whose ~312385 databases 34 contain entries for ~he object in this operation.
Similarly, if the service request requires deletion of an object, the control module 34 enables the deletion of the object from the database 34 and enables the transaction agent 31 to update the databases 34 in other nameservers 30 to reflect deletion of the object.
In this operation, the transaction agent also uses the DIR MAIN PROT directory maintenance protocol in enabling the operation and the attributes in the database 34 identifying other nameservers 30 whose databases contain entries for the object.
In performing an update, whether in response to a service request from a clerk 20 reguiring creation or deletion of an entry or in response to a service request from a clerk 20 reguiring transmission of updates to other nameservers, the transaction agent 31 us~ the update sender module 32. The transaction ~e~ 31, using the DIR MAIN PROT directory maintenance protocol, verifies other nameservers 30 whose databases 34 maintain entries associated with directories which require updating. For entries for other objects, and to perform the actual updating of entries relating to the directories, the update sender module 32 and update receiver modules 33 of identified nameservers 30 transfer update information using an UPD PROT update protocol.
If a service request from a clerk 20 requires a ~ c:. cc~ ~ 0~
return of information, such as the ~it~n of an identified object, if the nameserver 30 receiving the request can service the request, the transaction agent 31 returns the requested information to the clerk 20 using the CLK SERV PROT clerk service protocol. The information returned may include, for example, only the g location information, or it may include all attributes re].ating -to an entry, the identification of subdirectories of a directory, or whether an attribute in an entry has a value specified in the service request.
In addition to transmitting updates to other nameservers 30 in response to a service request therefor from a clerk 20 in a client node ll, the control module 35 in each nameserver 30 also initiates transmission of updates periodically. If a nameserver 30 is unable to accept an update operation, for example, if its server node lO is busy or not operational at the time, the nameserver 30 which initiated the update will retry as specified in the convergence at~tr1b~ute for the entry and -~ the relationship between the ~t-t-r-i~e specifying the date of the last update and the attribute identifying how up to date entries for the directory are to be.
The foregoing description has been limited to a specific embodiment of this invention. It will be apparent, however, that variations and modifications may be made -to the invention, with the attainment of some or all of the advantages of the invention. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the invention.
A benefit of providing only a single computer for a large number of users was that the users could easily share information. Thus, for example, if all persons working in a bookkeeping or accounting department use a single common computer, they may maintain common accounting and bookkeeping databases up to date, and when necessary accounting reports may be generated from those databases. However, if they use separate computers, the data is stored in separate databases, on each computer, and so generating accounting reports would be more difficult.
As a result, networks were developed to provide a distributed computer system, that is, a system which permits diverse computers to communicate and transfer data among them. In addition, the networks allow the :
:: :
~312385 sharing of expensive input/output devices, such as printers and mass storage devices, and input/output devices which may be rarely used, such as links to the public telecommunications network. In a network, each computer is a node which communicates with other nodes over one or several wires. In addition, nodes may be provided which store and manage databases or other data files on mass storage devices, or which manage printers or links to the public telecommunications network.
A problem arises with networks, however, since resources used in the network, such as programs and data files, the input/output devices and so forth, are typically stored in, or connected to, only some of the nodes. If clients on other nodes need to use such resources, they must be able to find them. In the past, each client node had to maintain a file identifying the location, within the network, of all resources which were available to the client. With a large network with many resources, this arrangement required substantial amounts of memory at each client node devoted only to the storage of such location information. In addition, maintaining location information in the diverse client nodes in an updated and current condition was difficult and required processing by the client node and transfers over the network which could otherwise be used for more useful information processing purposes.
More recently, naming services have been developed which maintained the identification of the locations of the resources available in a network. Naming services maintain the location information in only a few locations in the network, and provide the information to a client node on reguest. In addition, the naming services update the location information over the network without client node processing.
~312385 SUMMARY OF_ THE INVENTION
The invention provides a new and improved naming service for use in a network.
In brief summary, the present invention provides a naming service for use ln 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 fox responding -to name service requests from said client nodes; B. a clerk means in each of said client nodes for transmittin~ service request messages to initiate selected operations, said service request messages including database update request messages for causing entries of said database ~o be updated; C. a name server means in each of at least two of said server nodes, 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 databaæe entries; iii. update means for updating said entries in response to said database ~; update request messages; iv. update transfer means connected to said communications link ior transferring database update requests and database updates over said communications link from said name server means to other server nodes containing name server means;
and v. control means connected to said transaction agent means, : sald data base means, and said update transfer means for enabling : said update transfer means and said data base means to engage in an update operation cooperatively with another server node containing name server means in response to a database update ~ ~B
60~12-1825 request message received by said transaction agent means.
According to another aspect, the invention provides a method for use by a name service distributed between at least two server nodes in a system having a plurality of clien~ nodes and a plurallty of server nodes interconnected by a communications link for updating a plurality of name service database entries, each of each said database entries containing attributes associated with an object, said database entries being distributed among said server nodes con~aining said name service, said method comprising the steps of: a. receiving from a cllent node at one of said ; server nodes containing said name service a request for service which includes updating said database, b. checking whether said one of said server nodes is an appropriate node to respond to said request for service, c. passing said request for service to an appropria~e service node if said one of said server nodes is not an appropriate node to respond to said request for service, and d.
performing said database update reguest including passing corresponding database updates to another said server node containing said name service.
BRIEF DESCRIPTION_OF THE DRAWINGS
This invention is pointed out with particularity in the appended claims. The above and further advantages of this invention may be better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:
Fig. 1 is a general block diagram of a distributed 3a 60~l2-læ2s digital data processing system con~tructed in accordance with the invention;
Fig. 2 is another block diagram useful in understanding the invention.
DETAILED DESCRIPTION OF AN ILLUSTRATIVE FMBODIMENT
Fig. 1 is a general block diagram of a distributed digital data processing system constructed in accordance with the invention. With reference to Fig. 1, the system includes a plurality of nodes, including server nodes lOA throuyh 10N
(generally identified by reference 3b 4 60~12-1~25 numeral 10) and a plurality oE cllent nodes llA through llN
(generally identifled by reference numeral 11) lnterconnected by a communlcatlons llnk 12. The server nodes 10 provide a number of servlces to cllent no~es 11. The cllent nodes 11 are used by users to perform or lnltlate data processlng. Examples of ser-vlces provlded by server nodes 11 lnclude prlntlng and telecom-munlcatlons services, data processlng, mass storage backup of data whlch is processe~ by the cllent nodes 11 or by a server node 10, and common database control for client nodes 11, allowlng a plur-allty of cllent nodes to acce~s a common database. It wlll beappreclated that not all server nodes provlde all of such servlces to the cllent nodes 10; ln some cases, one or only a few server nodes 10 may provlde a partlcular servlce to the cllent nodes 11.
In addltlon, some of the server nodes 10 may provlde multlple ser-vices to the cllent nodes 11.
At least one server node 10 ln the system provldes a naming servlce 13. In brlef, a namlng service provides from a slngle locatlon, namely the server node contalnlng the namlng servlce, the locatlon of any ob~ect in server nodes 10 and client nodes 11 whlch ~ay be accessed by a client node 11. An object is typically a flle, for example, a program or a data flle, whlch ls ldentlfled by a name, or a directory, whlch may contain a file or other directory, which ls also identified by a name, or any other addressable resource in the system. A client node 11 whlch re-qulres access to an ob~ect, provldes the namlng servlce 13 wlth the name of the ob~ect, and the namlng servlce identlfles the client node 11 or server node 10 which controls the ob~ect and through whlch the ob~ect can be accessed. Dependlng on the number of ob~ects, client nodes 11 and server nodes lo, the naming service may be divided among several server nodes lo.
In particular, the naming service provides a database having a plurality of entries each associated with an object. Each server node 10 which serves to maintain portions of the naming service contains part, but not necessarily all, of a copy of the database; that is, portions of the database may be maintained on several of the server nodes 10 which form part of the database. Parts of the database may be replicated among the various server nodes 10.
The database entries contain attributes for each of the objects. In one embodiment, attributes include such information as the object identifier, an update timestamp, access rights to the object, and the network address of the object. If the object is a directory, the directory may reside at more than one location, and if so the directory will have a network address for each ~ ~ c ~
~ ca~t-~. In addition, if an object is a directory, its entry may be replicated in several of the server nodes 10, and attributes associated with each directory entry identify the locations of the directory in the network, how up to date each location is, and a convergence attribute which specifies the degree of effort required to be expended to maintain the directory's replicas up to date. An entry for a directory also identifies its relationship with other directories, in a system which maintains tree-structured directories.
Fig. 2 depicts a block diagram of modules in the naming service in the system depicted in Fig. 1. The naming service includes a clerk 20, which actually resides in all of the client hodes 11, and one or more nameservers generally identified by reference numeral 30, with each nameserver 30 residing in a server node - 6 - 13t2385 10. The clerk 20 provides the client interface to enable a client node 11 to communicate with the nameservers 30 in the various server nodes 10.
The nameservers 30 are all similar and so one nameserver, namely nameserver 3OA, will be described in detail. Nameserver 30A includes a transaction agent module 31A which communicates with the clerks 20, an update sender module 32A and an update receiver module 33A, which respectively communicate to other nameservers 30 changes to a database 34A and receive from other nameservers 30 and enter changes for the database 34.
Database 34 is the portion of the name service database resident on the particular nameserver. A control module 35A controls accesses to the database, and the operation of the transaction agent 31A, update sender 32A and update receiver 33A.
More specifically, periodically the transaction agent 31 in the nameserver 30 in each of the server nodes 10 which forms part of the naming service broadcasts over the communications iink 12 a solicitation advertising message, using a SOL ADV PROT
solicitation advertising protocol, notifying the clerks 20 in all of the client nodes 11 of their existence.
When the client node 11 requires service from a nameserver, it transmits, usi.ng a CLK SERV PROT clerk server protocol, a service request. A client node 11 may require service for several reasons. For example, the client node may need to access an object or obtain information about an object, such as the various subdirectories of a directory. Alternatively, a client node 11 may need to create an object, particularly a directory or a file, delete an object, or modify various attributes, such as access rights, with respect to an object. In addition, a client node may require a directory to be backed up. To initiate these services, the client node 11, through its clerk, transmits a service request to a transaction agent 31 about which it previously learned from the transaction agent's prior solicitation advertising message.
The transaction agent 31 receives the service request from the clerk and communicates with its control module to determine whether the nameserver 30 is the proper one to service the request. The control module 35 must first determine, from the records in data base 34, whether it maintains entries relating to the object, if it is to be deleted, backed up or accessed, or if it maintains the directory in which the object is to be created if a new object is to be created. If it does, it may accept the service request. If it does not, the control module 35 enables the transaction agent 31 to either refuse the service request or to transmit the service request to another nameserver 30, also using the CLK SERV PROT in communication with the transaction agent 31 of the other nameserver 30.
If the service request can be performed by a nameserver 30, the control module 35 enables operations which depend on the particular service request. For example, if the service request requires creation of an object, the control module 35 creates a new entry in the database 34 for the object and enters the various attributes. If an object is created in a directory, the control module at some point enables transaction agent 31 to update entries relating to the directory in databases 34 in other nameservers 30 to reflect creation of the object in the directory using a DIR MAIN PROT
directory maintenance protocol. The transaction agent 31 uses the attributes in the object's entry in the database 34 identifying other nameservers 30 whose ~312385 databases 34 contain entries for ~he object in this operation.
Similarly, if the service request requires deletion of an object, the control module 34 enables the deletion of the object from the database 34 and enables the transaction agent 31 to update the databases 34 in other nameservers 30 to reflect deletion of the object.
In this operation, the transaction agent also uses the DIR MAIN PROT directory maintenance protocol in enabling the operation and the attributes in the database 34 identifying other nameservers 30 whose databases contain entries for the object.
In performing an update, whether in response to a service request from a clerk 20 reguiring creation or deletion of an entry or in response to a service request from a clerk 20 reguiring transmission of updates to other nameservers, the transaction agent 31 us~ the update sender module 32. The transaction ~e~ 31, using the DIR MAIN PROT directory maintenance protocol, verifies other nameservers 30 whose databases 34 maintain entries associated with directories which require updating. For entries for other objects, and to perform the actual updating of entries relating to the directories, the update sender module 32 and update receiver modules 33 of identified nameservers 30 transfer update information using an UPD PROT update protocol.
If a service request from a clerk 20 requires a ~ c:. cc~ ~ 0~
return of information, such as the ~it~n of an identified object, if the nameserver 30 receiving the request can service the request, the transaction agent 31 returns the requested information to the clerk 20 using the CLK SERV PROT clerk service protocol. The information returned may include, for example, only the g location information, or it may include all attributes re].ating -to an entry, the identification of subdirectories of a directory, or whether an attribute in an entry has a value specified in the service request.
In addition to transmitting updates to other nameservers 30 in response to a service request therefor from a clerk 20 in a client node ll, the control module 35 in each nameserver 30 also initiates transmission of updates periodically. If a nameserver 30 is unable to accept an update operation, for example, if its server node lO is busy or not operational at the time, the nameserver 30 which initiated the update will retry as specified in the convergence at~tr1b~ute for the entry and -~ the relationship between the ~t-t-r-i~e specifying the date of the last update and the attribute identifying how up to date entries for the directory are to be.
The foregoing description has been limited to a specific embodiment of this invention. It will be apparent, however, that variations and modifications may be made -to the invention, with the attainment of some or all of the advantages of the invention. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the invention.
Claims (7)
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, 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;
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 to other server nodes containing name server means;
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.
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, 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;
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 to other server nodes containing name server means;
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 method for use by a name service distributed between at least two server nodes in a system having a plurality of client nodes and a plurality of server nodes interconnected by a communications link for updating a plurality of name service database entries, each of each said database entries containing attributes associated with an object, said database entries being distributed among said server nodes containing said name service, said method comprising the steps of:
a. receiving from a client node at one of said server nodes containing said name service a request for service which includes updating said database, b. checking whether said one of said server nodes is an appropriate node to respond to said request for service, c. passing said request for service to an appropriate service node if said one of said server nodes is not an appropriate node to respond to said request for service, and d. performing said database update request including passing corresponding database updates to another said server node containing said name service.
a. receiving from a client node at one of said server nodes containing said name service a request for service which includes updating said database, b. checking whether said one of said server nodes is an appropriate node to respond to said request for service, c. passing said request for service to an appropriate service node if said one of said server nodes is not an appropriate node to respond to said request for service, and d. performing said database update request including passing corresponding database updates to another said server node containing said name service.
3. The method of claim 2 wherein said client node passes said request for service through a clerk in one of said server nodes, said clerk providing an interface to said name service distributed between said server nodes.
4. The method of claim 2 wherein said name service distributed between said server nodes receives said request for service through a transaction agent in one of said server nodes, said transaction agent providing an interface to said client node.
5. The method of claim 2 wherein said name service distributed between said server nodes periodically broadcasts to said client nodes an availability to respond to said request for service.
6. The method of claim 2 wherein said database entries include information concerning which said server nodes containing said name service have related database entries.
7. The method of claim 2 wherein said database entries are updated periodically regardless of whether said request for service is received.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US9388287A | 1987-09-08 | 1987-09-08 | |
| US093,882 | 1987-09-08 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA1312385C true CA1312385C (en) | 1993-01-05 |
Family
ID=22241513
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA000576625A Expired - Fee Related CA1312385C (en) | 1987-09-08 | 1988-09-07 | Naming service for networked digital data processing system |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US5408619A (en) |
| EP (1) | EP0338041B1 (en) |
| JP (1) | JPH01502786A (en) |
| CA (1) | CA1312385C (en) |
| DE (1) | DE3889904T2 (en) |
| WO (1) | WO1989002631A1 (en) |
Families Citing this family (87)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2048306A1 (en) * | 1990-10-02 | 1992-04-03 | Steven P. Miller | Distributed configuration profile for computing system |
| GB9121348D0 (en) * | 1991-10-09 | 1991-11-20 | Trident Trade And Management S | Data bank update system |
| GB2263797B (en) * | 1992-01-31 | 1996-04-03 | Plessey Telecomm | Object orientated system |
| US5628011A (en) * | 1993-01-04 | 1997-05-06 | At&T | Network-based intelligent information-sourcing arrangement |
| US5511208A (en) * | 1993-03-23 | 1996-04-23 | International Business Machines Corporation | Locating resources in computer networks having cache server nodes |
| JP2541460B2 (en) * | 1993-07-30 | 1996-10-09 | 日本電気株式会社 | User status broadcasting with transmission restrictions |
| GB2281793A (en) * | 1993-09-11 | 1995-03-15 | Ibm | A data processing system for providing user load levelling in a network |
| AU6702594A (en) | 1993-12-17 | 1995-07-03 | Taligent, Inc. | Object-oriented distributed communications directory service |
| US5594921A (en) * | 1993-12-17 | 1997-01-14 | Object Technology Licensing Corp. | Authentication of users with dynamically configurable protocol stack |
| US5548726A (en) * | 1993-12-17 | 1996-08-20 | Taligeni, Inc. | System for activating new service in client server network by reconfiguring the multilayer network protocol stack dynamically within the server node |
| US5519855A (en) * | 1994-01-14 | 1996-05-21 | Microsoft Corporation | Summary catalogs |
| US5560005A (en) * | 1994-02-25 | 1996-09-24 | Actamed Corp. | Methods and systems for object-based relational distributed databases |
| US5490088A (en) * | 1994-02-28 | 1996-02-06 | Motorola, Inc. | Method of handling data retrieval requests |
| US6141663A (en) * | 1994-03-18 | 2000-10-31 | Unimax Systems Corporation | Automatic external data synchronization method |
| US5586312A (en) * | 1994-10-11 | 1996-12-17 | Unisys Corporation | Method and apparatus for using an independent transaction processing application as a service routine |
| US5577240A (en) * | 1994-12-07 | 1996-11-19 | Xerox Corporation | Identification of stable writes in weakly consistent replicated databases while providing access to all writes in such a database |
| US5603026A (en) * | 1994-12-07 | 1997-02-11 | Xerox Corporation | Application-specific conflict resolution for weakly consistent replicated databases |
| US5581754A (en) * | 1994-12-07 | 1996-12-03 | Xerox Corporation | Methodology for managing weakly consistent replicated databases |
| US5799157A (en) * | 1994-12-13 | 1998-08-25 | Elcom Systems, Inc. | System and method for creating interactive electronic systems to present information and execute transactions |
| US5617568A (en) * | 1994-12-14 | 1997-04-01 | International Business Machines Corporation | System and method for supporting file attributes on a distributed file system without native support therefor |
| US5832487A (en) * | 1994-12-15 | 1998-11-03 | Novell, Inc. | Replicated object identification in a partitioned hierarchy |
| US5706501A (en) * | 1995-02-23 | 1998-01-06 | Fuji Xerox Co., Ltd. | Apparatus and method for managing resources in a network combining operations with name resolution functions |
| US5592611A (en) * | 1995-03-14 | 1997-01-07 | Network Integrity, Inc. | Stand-in computer server |
| US5784570A (en) * | 1995-04-07 | 1998-07-21 | At&T Corp | Server for applying a recipient filter and compressing the input data stream based upon a set of at least one characteristics in a multiuser interactive virtual environment |
| US5632011A (en) * | 1995-05-22 | 1997-05-20 | Sterling Commerce, Inc. | Electronic mail management system for operation on a host computer system |
| US5664185A (en) * | 1995-05-22 | 1997-09-02 | Sterling Commerce, Inc. | Nameserver administration system and method |
| US6240451B1 (en) * | 1995-05-25 | 2001-05-29 | Punch Networks Corporation | Method and apparatus for automatically disseminating information over a network |
| US5694596A (en) * | 1995-05-25 | 1997-12-02 | Kangaroo, Inc. | On-line database updating network system and method |
| US5701451A (en) | 1995-06-07 | 1997-12-23 | International Business Machines Corporation | Method for fulfilling requests of a web browser |
| CA2227432C (en) * | 1995-07-20 | 2001-05-22 | Novell, Inc. | Transaction synchronization in a disconnectable computer and network |
| EP0839352B1 (en) | 1995-07-20 | 2002-10-16 | Novell, Inc. | Transaction log management in a disconnectable computer and network |
| CA2162188C (en) * | 1995-11-06 | 1999-05-25 | Harold Jeffrey Gartner | Location transparency of distributed objects over multiple middlewares |
| US7930340B2 (en) * | 1995-11-13 | 2011-04-19 | Lakshmi Arunachalam | Network transaction portal to control multi-service provider transactions |
| US8271339B2 (en) * | 1995-11-13 | 2012-09-18 | Lakshmi Arunachalam | Method and apparatus for enabling real-time bi-directional transactions on a network |
| US8037158B2 (en) * | 1995-11-13 | 2011-10-11 | Lakshmi Arunachalam | Multimedia transactional services |
| US5802510A (en) * | 1995-12-29 | 1998-09-01 | At&T Corp | Universal directory service |
| US5832221A (en) * | 1995-12-29 | 1998-11-03 | At&T Corp | Universal message storage system |
| US5826010A (en) * | 1996-02-12 | 1998-10-20 | Banyan Systems, Inc. | Predefined access rights for undefined attributes in a naming service |
| US5794232A (en) * | 1996-03-15 | 1998-08-11 | Novell, Inc. | Catalog services for distributed directories |
| US6662240B1 (en) * | 1996-05-08 | 2003-12-09 | Ncr Corporation | Automated configuration of computer accessories |
| US5857201A (en) * | 1996-06-18 | 1999-01-05 | Wright Strategies, Inc. | Enterprise connectivity to handheld devices |
| US6014686A (en) * | 1996-06-21 | 2000-01-11 | Telcordia Technologies, Inc. | Apparatus and methods for highly available directory services in the distributed computing environment |
| US6412017B1 (en) * | 1996-07-01 | 2002-06-25 | Microsoft Corporation | Urgent replication facility |
| US5878434A (en) * | 1996-07-18 | 1999-03-02 | Novell, Inc | Transaction clash management in a disconnectable computer and network |
| US5919247A (en) * | 1996-07-24 | 1999-07-06 | Marimba, Inc. | Method for the distribution of code and data updates |
| US5819287A (en) * | 1996-07-30 | 1998-10-06 | Nec Corporation | Database driven automatic program production system |
| US5790789A (en) * | 1996-08-02 | 1998-08-04 | Suarez; Larry | Method and architecture for the creation, control and deployment of services within a distributed computer environment |
| US6757729B1 (en) * | 1996-10-07 | 2004-06-29 | International Business Machines Corporation | Virtual environment manager for network computers |
| US6647393B1 (en) * | 1996-11-22 | 2003-11-11 | Mangosoft Corporation | Dynamic directory service |
| FR2759517B1 (en) * | 1997-01-24 | 1999-03-05 | Bull Sa | COMPUTER SYSTEM WITH DISTRIBUTED DATA STORAGE |
| US5995999A (en) * | 1997-03-12 | 1999-11-30 | Fujitsu Limited | Naming system for hierarchically named computer accessible objects |
| DE19747583B4 (en) | 1997-10-28 | 2006-04-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Communication system and method |
| KR100583011B1 (en) * | 1997-10-28 | 2006-05-24 | 텔레폰악티에볼라겟엘엠에릭슨(펍) | Communication system and method |
| US5995964A (en) * | 1997-12-10 | 1999-11-30 | Nihon Unisys, Ltd. | Managing first and second handles used in communication with an apparatus connected to a network |
| US6185655B1 (en) | 1998-01-22 | 2001-02-06 | Bull, S.A. | Computer system with distributed data storing |
| US6026414A (en) * | 1998-03-05 | 2000-02-15 | International Business Machines Corporation | System including a proxy client to backup files in a distributed computing environment |
| US6496862B1 (en) | 1998-08-25 | 2002-12-17 | Mitsubishi Electric Research Laboratories, Inc. | Remote monitoring and control of devices connected to an IEEE 1394 bus via a gateway device |
| US6505255B1 (en) | 1999-04-29 | 2003-01-07 | Mitsubishi Electric Information Technology Center America, Inc. (Ita) | Method for formatting and routing data between an external network and an internal network |
| US6961748B2 (en) | 1998-10-27 | 2005-11-01 | Murrell Stephen J | Uniform network access |
| US6421701B1 (en) * | 1999-01-29 | 2002-07-16 | International Business Machines Corporation | Method and system for replication support in a remote method invocation system |
| US6510450B1 (en) | 1999-02-04 | 2003-01-21 | Novell, Inc. | Multiple storage class distributed nametags for locating items in a distributed computing system |
| US6594702B1 (en) * | 1999-02-25 | 2003-07-15 | Oracle International Corporation | Managing the size and accessibility of a name service |
| EP1045304A1 (en) * | 1999-04-16 | 2000-10-18 | Martine Naillon | Method for controlling a decision process seeking a goal in a determined application domain, such as economical, technical, organisational or analogous and system for performing the method |
| US6633547B1 (en) | 1999-04-29 | 2003-10-14 | Mitsubishi Electric Research Laboratories, Inc. | Command and control transfer |
| US6378000B1 (en) | 1999-04-29 | 2002-04-23 | Mitsubish Electric Research Laboratories, Inc | Address mapping in home entertainment network |
| US6523064B1 (en) | 1999-04-29 | 2003-02-18 | Mitsubishi Electric Research Laboratories, Inc | Network gateway for collecting geographic data information |
| US6996627B1 (en) | 1999-05-25 | 2006-02-07 | Realnetworks, Inc. | System and method for providing update information |
| US7062765B1 (en) | 1999-05-25 | 2006-06-13 | Realnetworks, Inc. | System and method for updating information via a network |
| US6553384B1 (en) | 1999-06-14 | 2003-04-22 | International Business Machines Corporation | Transactional name service |
| GB2354611B (en) * | 1999-06-14 | 2004-02-11 | Ibm | A transactional name service |
| KR20010016708A (en) * | 1999-08-02 | 2001-03-05 | 문정훈 | Controlling apparatus for network traffic using a name server and controlling method for the same |
| US6449657B2 (en) | 1999-08-06 | 2002-09-10 | Namezero.Com, Inc. | Internet hosting system |
| US6961763B1 (en) * | 1999-08-17 | 2005-11-01 | Microsoft Corporation | Automation system for controlling and monitoring devices and sensors |
| US7139790B1 (en) | 1999-08-17 | 2006-11-21 | Microsoft Corporation | Weak leader election |
| US7133729B1 (en) | 1999-08-17 | 2006-11-07 | Microsoft Corporation | Pattern-and model-based power line monitoring |
| DE10049619A1 (en) * | 2000-10-05 | 2002-04-18 | Alcatel Sa | Process for the provision of services in a network management system with an open system architecture as well as a service object, requirement object and requirement manager for this |
| EP1199678A1 (en) * | 2000-10-17 | 2002-04-24 | Martine Naillon | Method for controlling a decision process seeking a goal in a determined application domain, such as economical, technical, organisational or analogous |
| US6651060B1 (en) | 2000-11-01 | 2003-11-18 | Mediconnect.Net, Inc. | Methods and systems for retrieval and digitization of records |
| US7185013B2 (en) * | 2001-04-12 | 2007-02-27 | International Business Machines Corporation | Method for constructing and caching a chain of file identifiers and enabling inheritance of resource properties in file systems |
| US20030050971A1 (en) * | 2001-09-10 | 2003-03-13 | Fuji Xerox Co., Ltd. | Client server system and method therefor |
| JP2003167862A (en) * | 2001-11-30 | 2003-06-13 | Nec Corp | Device, method and program for specifying location of object in distributed object system |
| US20030167330A1 (en) * | 2002-03-01 | 2003-09-04 | Cohen Norman H. | Continual rebinding of data sources |
| US9235457B2 (en) * | 2003-03-27 | 2016-01-12 | Oracle International Corporation | Proactively communicating information between processes through a message repository |
| US7653642B2 (en) * | 2004-11-30 | 2010-01-26 | Microsoft Corporation | Auto quota |
| US8380530B2 (en) | 2007-02-02 | 2013-02-19 | Webmd Llc. | Personalized health records with associative relationships |
| US8271649B2 (en) | 2007-08-30 | 2012-09-18 | Nokia Corporation | Access rights used for resource discovery in peer-to-peer networks |
| US9240971B2 (en) | 2011-11-16 | 2016-01-19 | LabTech, LLC | Automated management of generalized central name services by distributed remote devices |
Family Cites Families (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4423414A (en) * | 1981-08-27 | 1983-12-27 | Burroughs Corporation | System and method for name-lookup in a local area network data communication system |
| US4558413A (en) * | 1983-11-21 | 1985-12-10 | Xerox Corporation | Software version management system |
| US4644468A (en) * | 1984-07-20 | 1987-02-17 | International Business Machines Corp. | Name usage support through distributed processing networks linked by bridges and/or gateways |
| US4769772A (en) * | 1985-02-28 | 1988-09-06 | Honeywell Bull, Inc. | Automated query optimization method using both global and parallel local optimizations for materialization access planning for distributed databases |
| US4754395A (en) * | 1985-05-06 | 1988-06-28 | Computer X, Inc. | Network interface module with minimized data paths |
| US4694396A (en) * | 1985-05-06 | 1987-09-15 | Computer X, Inc. | Method of inter-process communication in a distributed data processing system |
| CA1252903A (en) * | 1985-06-11 | 1989-04-18 | Frank D. Bartocci | Dynamic update of database directories using directed or undirected mechanisms |
| US4710870A (en) * | 1985-07-10 | 1987-12-01 | Bell Communications Research, Inc. | Central computer backup system utilizing localized data bases |
| US4714995A (en) * | 1985-09-13 | 1987-12-22 | Trw Inc. | Computer integration system |
| US4825354A (en) * | 1985-11-12 | 1989-04-25 | American Telephone And Telegraph Company, At&T Bell Laboratories | Method of file access in a distributed processing computer network |
| US4800488A (en) * | 1985-11-12 | 1989-01-24 | American Telephone And Telegraph Company, At&T Bell Laboratories | Method of propagating resource information in a computer network |
| US4714992A (en) * | 1985-11-26 | 1987-12-22 | International Business Machines Corporation | Communication for version management in a distributed information service |
| US4747130A (en) * | 1985-12-17 | 1988-05-24 | American Telephone And Telegraph Company, At&T Bell Laboratories | Resource allocation in distributed control systems |
| US5047918A (en) * | 1985-12-31 | 1991-09-10 | Tektronix, Inc. | File management system |
| US4925311A (en) * | 1986-02-10 | 1990-05-15 | Teradata Corporation | Dynamically partitionable parallel processors |
| JP2585535B2 (en) * | 1986-06-02 | 1997-02-26 | 株式会社日立製作所 | Process connection method in compound computer system |
| US4780821A (en) * | 1986-07-29 | 1988-10-25 | International Business Machines Corp. | Method for multiple programs management within a network having a server computer and a plurality of remote computers |
| US4819159A (en) * | 1986-08-29 | 1989-04-04 | Tolerant Systems, Inc. | Distributed multiprocess transaction processing system and method |
| US4845658A (en) * | 1986-12-01 | 1989-07-04 | Massachusetts Institute Of Technology | Information method and apparatus using simplex and duplex communications |
| US4914571A (en) * | 1987-06-15 | 1990-04-03 | International Business Machines Corporation | Locating resources in computer networks |
| US4881166A (en) * | 1987-07-24 | 1989-11-14 | Amoco Corporation | Method for consistent multidatabase transaction processing |
| US4853843A (en) * | 1987-12-18 | 1989-08-01 | Tektronix, Inc. | System for merging virtual partitions of a distributed database |
-
1988
- 1988-09-01 DE DE3889904T patent/DE3889904T2/en not_active Expired - Fee Related
- 1988-09-01 WO PCT/US1988/003030 patent/WO1989002631A1/en active IP Right Grant
- 1988-09-01 EP EP88908584A patent/EP0338041B1/en not_active Expired - Lifetime
- 1988-09-07 CA CA000576625A patent/CA1312385C/en not_active Expired - Fee Related
-
1989
- 1989-05-08 JP JP63507521A patent/JPH01502786A/en active Pending
-
1993
- 1993-06-17 US US08/079,701 patent/US5408619A/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| EP0338041B1 (en) | 1994-06-01 |
| DE3889904D1 (en) | 1994-07-07 |
| US5408619A (en) | 1995-04-18 |
| EP0338041A1 (en) | 1989-10-25 |
| DE3889904T2 (en) | 1995-01-12 |
| WO1989002631A1 (en) | 1989-03-23 |
| JPH01502786A (en) | 1989-09-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA1312385C (en) | Naming service for networked digital data processing system | |
| EP0329779B1 (en) | Session control in network for digital data processing system which supports multiple transfer protocols | |
| US5227778A (en) | Service name to network address translation in communications network | |
| US6571278B1 (en) | Computer data sharing system and method for maintaining replica consistency | |
| US7035931B1 (en) | Volume location service for a distributed file system | |
| EP0837584B1 (en) | Inter-cache protocol for improved web performance | |
| US6081840A (en) | Two-level content distribution system | |
| CA1270066A (en) | Method of propagating resource information in a computer network | |
| US5630116A (en) | Automatic delivery system for master files in a distributed processing system | |
| US6023722A (en) | High-availability WWW computer server system with pull-based load balancing using a messaging and queuing unit in front of back-end servers | |
| US5144557A (en) | Method and system for document distribution by reference to a first group and particular document to a second group of user in a data processing system | |
| US5751962A (en) | Object-based systems management of computer networks | |
| JP4278299B2 (en) | Communication system and method | |
| CZ289563B6 (en) | Server computer connectable to a network and operation method thereof | |
| EP0810537A2 (en) | Network browsing system and method | |
| EP0756730A1 (en) | Data storage | |
| US6697859B1 (en) | Apparatus, method, program, and information processing system for prioritized data transfer to a network terminal | |
| US6687221B1 (en) | Communication management control system, communication control unit therefor and computer program product | |
| US6519610B1 (en) | Distributed reference links for a distributed directory server system | |
| JPH04167159A (en) | Serve retrieving method for network system | |
| Zhou | The design and implementation of the Berkeley Internet Name Domain (BIND) servers | |
| WO2001090943A2 (en) | Distributed internet content delivery system | |
| JP3516850B2 (en) | FAX management device | |
| JP3088305B2 (en) | Remote location report printing system | |
| JPH07105147A (en) | Automatic delivery system for master file of decentralized processing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| MKLA | Lapsed |