XML-based integrated services event system

• US 6,941,560 B1
• Filed: 05/25/2001
• Issued: 09/06/2005
• Est. Priority Date: 12/19/2000
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Johnson, Craig C., Fletcher, Samuel F., Lowry, Dale, Sievers, Kent
• Primary Examiner(s): EL HADY, NABIL M
• Application Number:
  US09/865,257
• Time in Patent Office: 1,565 Days
• Field of Search: 709/310, 709/201, 709/203, 709/223, 709/224, 709/227, 709/228, 709/230, 709/246, 719/315, 719/316, 719/317, 719/318, 719/328
• US Class Current: 719/328
• 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, method and software program is provided for distributed directory enabled applications using an XML API. The improvement provides an event system, a parser, and a bridge-based object model. The event system includes the ability to publish an event, subscribe to the event, and act on the event. The parser enables the XML API to parse XML files by accepting an XML file as an input stream, parsing the input stream, dynamically loading system services referenced in the input stream, and configuring the services. The bridge-based object model utilizes thread safeness, which enables a bridge to use semaphore access control to control thread access, smart pointers, which enable a bridge to automatically manage the memory it requires, and opaque interfaces, which allow a bridge to maintain interface compatibility when implementation changes occur in an interface.

Claims

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

XML”

) application program interface (“

API”

), the interface including at least one event delineated by an event parameter, the event defining an object delineated by an object property and an object parameter, the method comprising;

accepting one or more applications as subscribers to the event;

defining one or more subscription filters for each of the subscribers, thereby allowing the subscribers to selectively filter the event;

publishing the event;

retrieving a subscriber list, the list including the one or more subscribers and the one or more subscription filters; and

;

automatically and sequentially passing the event to each subscriber on the list having associated filters that allow the event to pass and allowing such subscribers to act on the event until the subscriber list is exhausted or the event terminated.

2. The method of claim 1 further including filtering the event through an event filter based on the event parameter.

3. The method of claim 2 further including acting on the event by altering the event parameter, so that the event is transformed through the alteration.

4. The method of claim 1 further including filtering the event through an object filter, whereby the event is filtered based on the object property.

5. The method of claim 4 further including acting on the event by altering the object property, so that the event is transformed through the alteration.

6. The method of claim 1 further including filtering the event through a parameter filter, whereby the event is filtered based on the object parameter.

7. The method of claim 6 further including acting on the event by altering the object parameter, so that the event is transformed through the alteration.

8. The method of claim 1 further including acting on the event by terminating the event, so that the event is stopped by the termination.

9. The method of claim 1 further including tracking the event, whereby information about the event may be gathered.

10. The method of claim 9 further including generating reports from the gathered information, so that the information about the event may be compiled.

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

XML”

) application program interface (“

API”

), the interface including at least one event delineated by an event parameter, the event defining an object delineated by an object property and an object parameter, the system comprising;

at least one processor;

at least one memory accessible to the processor;

a plurality of applications stored in a plurality of respective portions of the memory;

defining at least one subscription filter allowing a plurality of subscribers to selectively filter the event;

parsing the event with an XML parser;

instantiating the event as a Data Object Model (DOM) class when services required by the event are unavailable;

publishing the event by at least one of the plurality applications;

automatically passing the event to at least one of the plurality of applications if the event passes the at least one subscription filter; and

allowing at least one of the plurality of applications to act on the event.

12. The computer system of claim 11 further including instructions for filtering the event through an event filter, whereby the event is filtered based on the event parameter.

13. The computer system of claim 12 further including instructions for acting on the event by altering the event parameter, so that the event is transformed through the alteration.

14. The computer system of claim 11 further including instructions for filtering the event through an object filter, whereby the event is filtered based on the object property.

15. The computer system of claim 14 further including instructions for acting on the event by altering the object property, so that the event is transformed through the alteration.

16. The computer system of claim 11 further including instructions for filtering the event through a parameter filter, whereby the event is filtered based on the object parameter.

17. The computer system of claim 16 further including instructions for acting on the event by altering the object parameter, so that the event is transformed through the alteration.

18. The computer system of claim 11 further including instructions for acting on the event by terminating the event, so that the event is stopped by the termination.

19. The computer system of claim 11 further including instructions for tracking the event, whereby information about the event may be gathered.

20. The computer system of claim 19 further including instructions for generating reports from the gathered information, so that the information about the event may be compiled.

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

XML”

) application program interface, the interface including at least one event delineated by an event parameter, the event defining an object delineated by an object property and an object parameter, the method comprising;

defining at least one subscription filter allowing at least first and second subscribers to selectively filter the event;

publishing the event;

retrieving a subscriber list, the list including the first and second subscribers and the subscription filter;

selecting the first and second subscribers and the subscription filter from the list;

passing the event to the first subscriber if the event passes through a first subscription filter;

allowing the first subscriber to modify or terminate the event based on an alteration of at least one of the event parameter and the object parameter; and

passing the modified event to the second subscriber if the event is not terminated and the event passes through a second subscription filter.