XML-based integrated services bridging

• US 6,772,206 B1
• Filed: 06/11/2001
• Issued: 08/03/2004
• Est. Priority Date: 12/19/2000
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Lowry, Dale, Sievers, Kent, Fletcher, Samuel F.
• Primary Examiner(s): Alam, Hosain
• Assistant Examiner(s): Tran, Philip B.
• Application Number:
  US09/878,710
• Time in Patent Office: 1,149 Days
• Field of Search: 709/328, 709/315-318, 709/201, 709/203, 709/223-224, 709/227-228, 709/230, 709/246, 719/328
• US Class Current: 709/223
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

An improved system and method is provided for bridging in a distributed directory-enabled application environment using an eXtensible Markup Language (“XML”) application program interface, where the interface includes a preprocessor using a configuration file. The method includes establishing a set of foundational bridge components and a set of task specific bridge parameters which are defined in the configuration file. The bridge is dynamically generated so that it includes the components and parameters, which enable applications in the distributed environment to communicate. The set of foundational bridge components may include thread safeness, smart pointers, and opaque interfaces.

Claims

1. A method for providing bridges in a distributed directory-enabled application environment using an eXtensible Markup Language (“

XML”

) application program interface, the interface including a preprocessor using a configuration file, the method comprising;

implementing a set of foundational bridge components so that the bridge includes;

thread safeness, whereby a bridge utilizes semaphore access control to control thread access;

smart pointers, whereby the bridge automatically manages the memory it requires; and

opaque interfaces, whereby the bridge maintains interface compatibility when implementation changes occur in an interface, so that the bridge can perform tasks utilizing the foundational components;

establishing a set of task specific bridge parameters, the set of parameters being defined in the configuration file; and

dynamically generating the bridge to include the set of components and the set of parameters, so that applications in the distributed environment can communicate via the bridge.

2. The method of claim 1 further comprising:

dynamically generating the set of parameters from the configuration file.

3. The method of claim 2 further comprising:

providing cross-language capabilities for enabling applications using different languages to communicate through the bridge as one of the set of parameters.

4. The method of claim 2 further comprising:

providing cross implementation capabilities for enabling applications with implementation differences to communicate through the bridge as one of the set of parameters.

5. A computer system for providing bridges in a distributed directory-enabled application environment using an eXtensible Markup Language (“

XML”

) application program interface, the interface including a preprocessor using a configuration file, the system comprising;

at least one processor;

at least one memory accessible to the processor;

a first application stored in a first portion of the memory;

a second application stored in a second portion of the memory;

software for bridging between the first and second applications, the software comprising instructions for;

implementing a set of foundational bridge components so that the bridge includes thread safeness, whereby a bridge utilizes semaphore access control to control thread access;

smart pointers, whereby the bridge automatically manages the memory it requires; and

opaque interfaces, whereby the bridge maintains interface compatibility when implementation changes occur in an interface, so that the bridge can perform tasks utilizing the foundational components;

establishing a set of task specific bridge parameters, the set of parameters being defined in the configuration file; and

dynamically generating the bridge to include the set of components and the set of parameters, so that applications in the distributed environment can communicate via the bridges.

6. The computer system of claim 5, wherein the software further includes instructions for dynamically generating the set of parameters from the configuration file.

7. The computer system of claim 6, wherein the software further includes instructions for cross-language capabilities for enabling applications using different languages to communicate through the bridge as one of the set of parameters.

8. The computer system of claim 6, wherein the software further includes instructions for enabling applications with implementation differences to communicate through the bridge as one of the set of parameters.

9. A method for using an eXtensible Markup Language (“

XML”

) application program interface preprocessor for dynamically generating bridges using at least one configuration file in a distributed directory-enabled application environment, the method comprising;

defining a set of foundational bridge components to be used in each dynamically generated bridge, wherein defining the set of foundational bridge components includes;

implementing thread safeness, wherein a bridge utilizes semaphore access control to control thread access;

implementing smart pointers, wherein the bridge automatically manages the memory it requires; and

implementing opaque interfaces, wherein the bridge maintains interface compatibility when implementation changes occur in an interface;

defining a first set of task specific bridge parameters to be used only in a bridge that is dynamically generated for a specific task, wherein the first set of parameters are defined in the configuration file; and

dynamically generating a first bridge for the specific task to include the set of components and the first set of parameters.

10. The method of claim 9 further comprising:

defining a second set of task specific bridge parameters to be used only in a bridge that is dynamically generated for a specific task, wherein the second set of parameters are defined in the configuration file; and

dynamically generating a second bridge for the specific task to include the set of components and the second set of parameters.

11. The method of claim 9 further comprising using a plurality of configuration files to define a plurality of sets of task specific bridge parameters.