Data processing: software development – installation – and managem – Software program development tool – Translation of code
Reexamination Certificate
1999-05-07
2001-04-03
Chaki, Kakali (Department: 2122)
Data processing: software development, installation, and managem
Software program development tool
Translation of code
C717S152000, C717S152000, C717S152000, C717S152000, C709S241000, C709S241000
Reexamination Certificate
active
06212676
ABSTRACT:
TECHNICAL FIELD
The present invention relates generally to data processing systems and, more particularly, to an event system for reporting system management events in a data processing system.
BACKGROUND OF THE INVENTION
Many distributed operating systems have difficulty in monitoring events. In particular, these operating systems have difficulty determining where events occur and obtaining useful information about the events. Such systems do not provide a convenient architecture for raising and sending events.
SUMMARY OF THE INVENTION
In accordance with an aspect of the present invention, a method is practiced in a data processing system in which a global namespace of objects is provided and stored in the memory means. Event source objects are provided for generating event report objects in response to events at the event source objects. An event sink object is provided for receiving event report objects and a distributor object is also provided for distributing event report objects from the event source objects to the event sink objects. The event source objects, the event sink object, the distributor object and the event report objects are all visible in the global namespace. An event is triggered at one of the event source objects and an event report is generated in response to the event. The event report is generated at the event source object where the event was triggered. The event report object is forwarded to the distributor object. The distributor object forwards the event report object to the event sink object to inform the event sink object of the triggered event. The distributor object may be provided with a filter that is examined to determine where the report object should be forwarded.
In accordance with an additional aspect of the present invention, a plurality of event source objects are provided along with a plurality of event sink objects and a distributor object. The event sink objects are registered with the distributor object to be informed of events at the event source objects. Event report objects are generated at the event source objects in response to events. The event report objects are forwarded to the distributor object, and the distributor object determines which event sink object should receive the event report objects. Once this determination is made, the event report objects are forwarded to the determined event sink objects.
In accordance with a further aspect of the present invention, a method is practiced in a data processing system having a storage device. In this method an event source object is stored in the storage device. The event source object then raises events and generates event reports that report the generated events. Event sink objects are also stored in the storage device. An event source holder object is stored in the storage device. The event source holder object maintains a register of registrations by event source objects that are registered to receive an event report upon occurrence of an event at the event source object. An event is triggered at the event source object, and event reports are sent to event sink objects that are registered with the event source holder object.
In accordance with a still further aspect of the present invention, a method is practiced wherein an event source object is stored in the storage device. The event source object is capable of raising a set of events. Type information is stored about the event source object in the storage device. The type information specifies the set of events that the event source object may raise.
In accordance with a further aspect of the present invention, a method is practiced wherein at least one event source object is provided in the memory means for generating an event report in response to an event at the event source object. In addition, a first distributor object and a second distributor object are provided in the memory means. The first distributor object serves to distribute the event report when generated by the event source object to the second distributor object. An event is triggered at the event source object and the event report is generated at the event source object. The event report is forwarded to the first distributor object. Filtering information is provided from the second distributor object to the first distributor object. The filtering information specifies a type of event report that the second distributor object wishes to receive. Where the filtering information indicates that the second distributor object wishes to receive the event report, the event report is forwarded from the first distributor object to the second distributor object.
In accordance with a further aspect of the present invention, a method is practiced wherein an event source object for generating an event report in response to an event is provided along with an event sink object for receiving the event report. In this method, the event sink object is registered to receive the event report from the event source object. As part of the registration, an instance of a function in an interface to be called by the event report as received by the event sink object is specified.
REFERENCES:
patent: 4866638 (1989-09-01), Cosentino et al.
patent: 5155842 (1992-10-01), Rubin
patent: 5321838 (1994-06-01), Hensley et al.
patent: 5333302 (1994-07-01), Hensley et al.
patent: 5355484 (1994-10-01), Record et al.
patent: 5517655 (1996-05-01), Collins et al.
patent: 5551035 (1996-08-01), Arnold et al.
patent: 5566337 (1996-10-01), Szymanski et al.
patent: 5581760 (1996-12-01), Atkinson et al.
patent: 5692157 (1997-11-01), Williams
patent: 5794005 (1998-08-01), Steinman
patent: 5822583 (1998-10-01), Tabuchi
patent: 5838969 (1998-11-01), Jacklin et al.
patent: 5905890 (1999-05-01), Seaman et al.
patent: 5925108 (1999-07-01), Johnson et al.
patent: 5987423 (1999-11-01), Arnold et al.
patent: 6104963 (2000-08-01), Cebasek et al.
patent: WO91/03017 (1991-03-01), None
Richner et al., “Architecture of an MMS Event Manager”, IEEE, pp. 439-444, 1993.*
IBM, “Event Handlers For An Object-Oriented Officevision,”IBM Technical Disclosure Bulletin,34:No. 4A (Sep. 1991).
Microsoft Corporation,Microsoft Visual Basic Control Development Guide,Chapter 2, “Fundamental Concepts,” pp. 7-14; Chapter 8, “Adding Custom Events,” pp. 57-63 (1992).
Masoni, A., et al., “Performances of the Obelix Event Builder and Producer,”IEEE(1993).
Microsoft Press, Chapter 1, “Windows and Programming,” pp. 1-23; Chapter 5, “The Mouse,” pp. 169-171,Programming Windows(1988).
Heller, D., “The XView Toolkit,”UnixWorld,VII:No. 6, pp. 127-138 (Jun. 1990).
Heller, D., “The XView Notifier,”UnixWorld,VII:No. 7, pp. 123-133 (Jul. 1990).
Blanford Mark S.
Heizer Isaac J.
Plastina Daniel E. F.
Ross Kevin W.
Seaman Michael R. C.
Chaki Kakali
Christensen O'Connor Johnson & Kindness PLLC
Microsoft Corporation
Vo Ted T.
LandOfFree
Event architecture for system management in an operating system does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Event architecture for system management in an operating system, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Event architecture for system management in an operating system will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2509370