Directory server plug-in call ordering

• US 20080208960A1
• Filed: 02/28/2007
• Published: 08/28/2008
• Est. Priority Date: 02/28/2007
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Rowley, Peter, Hosol, Norlko
• Granted Patent: US 8,095,625 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06F 16/282 Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]

Abstract

A method and apparatus for ordering callbacks for server plug-ins of a Lightweight Directory Access Protocol (LDAP) directory server. Each plug-in registers with the LDAP server and has a designated priority and set of dependencies. The priority and dependency data are stored in an LDAP callback configuration entry or set of entries. The LDAP server analyzes the priority and dependencies to determine the order of each plug-in or individual callback relative to one another. This allows the LDAP directory server and LDAP operations to rely on the order of callbacks thereby improving the efficiency of the system.

Claims

1. A method comprising:

retrieving configuration data for a lightweight directory access protocol (LDAP) directory server plug-in, the configuration data including a callback order indicator; and

ordering callback data in a callback list based on the callback order indicator.

2. The method of claim 1, further comprising:

calling a plug-in initialization process.

3. The method of claim 1, further comprising:

receiving a registration request from the plug-in.

4. The method of claim 1, wherein retrieving configuration data further comprises:

retrieving a dependency attribute for the plug-in.

5. The method of claim 1, wherein retrieving configuration data further comprises:

retrieving a priority attribute for the plug-in.

6. The method of claim 1, wherein ordering call back data further comprises:

inserting the callback data into the callback list according to the callback order indicator.

7. The method of claim 1, further comprising:

processing calls according to the order of the callback list.

8. The method of claim 1, further comprising:

inserting a callback into the callback list individually.

9. The method of claim 8, wherein the callback order indicator indicates an order for executing an individual callback of the plug-in.

10. The method of claim 1, wherein the callback order indicator indicates an order for executing all callbacks of the plug-in.

23. The machine readable medium of claim 8, wherein the callback order indicator indicates an order for executing an individual callback of the plug-in.

24. The machine readable medium of claim 1, wherein the callback order indicator indicates an order for executing all callbacks of the plug-in.

11. A system comprising:

a lightweight directory access protocol (LDAP) directory server and;

an LDAP plug-in registration module, the LDAP plug-in registration module to access configuration data indicating plug-in callback order.

12. The system of claim 11, further comprising:

a plug-in initialization module in communication with the registration module, the initialization module to select a plug-in to load.

13. The system of claim 11, wherein the registration module retrieves a dependency attribute from the configuration data.

14. The system of claim 11, wherein the registration module inserts an individual callback into a callback order list.

15. A machine readable medium, having instructions stored therein, which when executed, cause a machine to perform a set of instructions comprising:

retrieving configuration data for a lightweight directory access protocol (LDAP) directory server plug-in, the configuration data including a callback order indicator; and

ordering callback data in a callback list based on the callback order indicator.

16. The machine readable medium of claim 15, having further instructions stored therein, which when executed perform a set of operations further comprising:

calling a plug-in initialization process.

17. The machine readable medium of claim 15, having further instructions stored therein, which when executed perform a set of operations further comprising:

receiving a registration request from the plug-in.

18. The machine readable medium of claim 15, wherein retrieving configuration data further comprises:

retrieving a dependency attribute for the plug-in.

19. The machine readable medium of claim 15, wherein retrieving configuration data further comprises:

retrieving a priority attribute for the plug-in.

20. The machine readable medium of claim 15, wherein ordering call back data further comprises:

inserting the callback data into the callback list according to the callback order indicator.

21. The machine readable medium of claim 15, having further instructions stored therein, which when executed perform a set of operations further comprising:

processing calls according to the order of the callback list.

22. The machine readable medium of claim 15, having further instructions stored therein, which when executed perform a set of operations further comprising:

inserting a callback into the callback list individually.