Computer system with preferential naming service

• US 6,438,590 B1
• Filed: 04/13/1999
• Issued: 08/20/2002
• Est. Priority Date: 04/13/1999
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Gartner, M. Scott, Simpson, Shell S.
• Primary Examiner(s): WILEY, DAVID ARMAND
• Application Number:
  US09/291,400
• Time in Patent Office: 1,225 Days
• Field of Search: 709/219, 709/226, 709/228, 717/3
• US Class Current: 709/219
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A computer system includes a distributed application program having shared objects on a client workstation and on a server. Installation of the application program assures that an object request broker, a preferential naming service (PNS), PNS registry, and a portion of the application program are executable on the client workstation. In operation, the application program makes a request of the PNS containing an object name and criteria for determining an object reference. The PNS accesses the PNS registry to select candidate records according to the object name and version criteria. In addition, for a tree structured registry, the PNS responds to scope criteria and cross references to identify candidates. A tree structured registry may include references to portions of other tree structured registries. The PNS determines a policy from a candidate record, then determines an object reference by applying the policy. When needed, the PNS activates a local object or contacts a naming service on the server to determine the object reference. The object reference is then provided to the application program. The policy may dictate that candidate records refer only to local objects, only to remote objects, that a local object if viable is preferred, or that a remote object if viable is preferred. The request may include a version criteria directing use of an exact version or use of a latest version.

Claims

1. A memory comprising indicia of a method for providing an object reference, the method executed on a first workstation, the method comprising:

in response to a request that originated on the first workstation, the request comprising a first object identifier, determining a policy in accordance with the first object identifier;

determining, in further response to the request, a selected object reference in accordance with the policy, wherein the policy governs selection between first indicia of a first object that would, if selected, execute on the first workstation and second indicia of a second object that would, if selected, execute on a second workstation; and

providing the selected object reference.

2. The memory of claim 1 wherein:

a. the request further comprises a version criteria; and

b. the step of determining a policy further comprises determining the policy in accordance with the version criteria.

3. The memory of claim 1 wherein for a particular policy the determination of the object reference avoids selecting the second object.

4. The memory of claim 1 wherein the method further comprises obtaining from a naming service a second object reference, the second object reference corresponding to the second object.

5. The memory of claim 4 wherein the step of obtaining is in further response to the request.

6. The memory of claim 1 wherein:

a. the request further includes a first scope; and

b. the step of determining the policy is performed in further accordance with the first scope.

7. The memory of claim 6 wherein the indicia of the second object comprises a second scope.

8. The memory of claim 1 wherein the step of determining the selected object reference further comprises activating on the first workstation an object corresponding to the first object identifier.

9. A memory comprising indicia of a method for installing an application program, the method comprising:

installing a first naming service on a first workstation;

forming a registry on the first workstation for use by the first naming service, the registry comprising an object identifier and a policy; and

installing the application program for execution at least in part on the first workstation so that the application program makes a first request to the first naming service to obtain an object reference in accordance with the policy;

wherein

the policy governs selection between first indicia of a first object that would, if selected, execute on the first workstation and second indicia of a second object that would, if selected, execute on a second workstation.

10. The memory of claim 9 wherein the step of forming the registry further comprises making a second request to a second naming service to obtain the object reference.

11. The memory of claim 10 wherein the method further comprises installing a finding service on a third workstation, the finding service for returning to the first naming service a third object reference for communication between the first naming service and the second naming service.

12. The memory of claim 9 wherein:

the registry existed on the first workstation prior to installation; and

the step of forming the registry comprises revising the registry in accordance with a strategy of the application program being installed.

13. The memory of claim 9 wherein the step of forming the registry comprises enabling the first naming service to obtain and to store a plurality of object references in the registry.

14. The memory of claim 9 wherein the memory further comprises indicia of at least one of the set consisting of the first naming service, the registry, and the object request broker.

15. A memory comprising indicia of a data structure, the data structure comprising:

a. a first object identifier; and

b. a policy for determining whether a first object reference is to be provided in response to a request, the request comprising a second object identifier corresponding to the first object identifier.

16. The memory of claim 15 wherein:

a. the request originates on a first workstation; and

b. the policy governs selection between first indicia of a first object that would, if selected, execute on the first workstation and second indicia of a second object that would, if selected, execute on a second workstation.

17. The memory of claim 15 wherein:

a. the first object identifier identifies an object having a version; and

b. the data structure further comprises a first version indicator corresponding to the version.

18. A plurality of component data structures individually comprising:

a first object identifier;

a policy for determining whether a first object reference is to be provided in response to a request, the request comprising a second object identifier corresponding to the first object identifier; and

a reference to a respective parent component data structure of the plurality of component data structures.

19. The data structure of claim 18 wherein:

a. each component data structure corresponds to a respective element of a tree graph, each respective element being related to other elements by one or more of the relationships of a set consisting of parent, child, and sibling; and

b. a first component data structure corresponding to a particular element further comprises a reference for determining a scope of a search, the reference being to a second data structure that is not related as a parent, is not related as a sibling, and is not related as a child.

20. The data structure of claim 18 wherein the reference identifies a folder of a second naming service.