Priority based LDAP service publication mechanism

• US 7,496,566 B2
• Filed: 08/03/2005
• Issued: 02/24/2009
• Est. Priority Date: 08/03/2005
• Status: Active Grant

• Current Assignee: Maplebear Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Piper, Scott A., Santana, Carlos, Bauman, Charles D., Pruett, Gregory
• Primary Examiner(s): To; Baoquoc N
• Application Number:
  US11/195,958
• Publication Number:
  US 20070050331A1
• Time in Patent Office: 1,301 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99936 Pattern matching access

Abstract

A method and system are provided for directing a client to a preferred service instance. At creation of a service instance, the service binding attribute of the created instance is extended to include assigned domains and associated priorities. There are then two phases to directing a client to the preferred service instance. The first phase is compilation of a list of domains and priorities for the service in response to a query. Upon completion of the first phase, a second phase is executed to determine a preferred service for the client by comparing fully qualified domain name entries and assigned priority entries.

Claims

1. A method for directing a client to a preferred service instance, comprising:

storing data in a service binding attribute of a service connection point, said data including adaptive domain data for domains served by said service instance and adaptive priority data associated with said domains, said priority data indicating quality of a match of an associated service instance to domain data;

querying a directory of compiled assigned domain and priority data to each service attribute for all instances of a service;

receiving a list of domain data associated with said priority data for each service instance in response to said query; and

scanning said list for a match for a client machine to a preferred service instance, including determining a preferred service instance for said client based upon;

a comparison of a domain data entry in said list with a domain data assignment to said client, and a comparison of a priority entry in said list with a priority assignment to said client responsive to a comparison of said domain data entries resulting in maintaining a current client assignment.

2. The method of claim 1, further comprising compiling a directory of assigned domain data and priority data associated with each service instance, including each item in said directory having a fully qualified domain name and an associated priority.

3. The method of claim 2, wherein said list includes one item per pair of fully qualified domain name and an associated priority.

4. The method of claim 1, wherein said priority data identifies closeness of said service instance to said domain.