Electrical computers and digital processing systems: multicomput – Computer-to-computer data routing – Least weight routing
Reexamination Certificate
1997-11-13
2003-03-11
Lao, Sue (Department: 2151)
Electrical computers and digital processing systems: multicomput
Computer-to-computer data routing
Least weight routing
Reexamination Certificate
active
06532498
ABSTRACT:
COPYRIGHT© 1994 TEXAS INSTRUMENTS INCORPORATED
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the United States Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a method and system for providing event notification between software application program objects.
BACKGROUND OF THE INVENTION
Most computer implemented software systems include a plurality of applications, each programmed to perform a specific function. An application is composed of several programs which in turn are composed of several modules or objects. In general, each of the program objects must, at one time or another, communicate information to another program object regarding events which occur within or under control of the object.
For general reference see Comer, Douglas E and Stevens, David L.,
Internetworking with TCP/IP,
vol. III, Prentice-Hall, (1993);
PIPES Platform User's Guide and Reference Maual,
PeerLogic, Inc., (1993); “X/Open Transport Interface (XTI)”,
X/Open CAE Specification,
X/Open Company limited, (1992); Stevens, W. Richard,
Unix Network Programming,
Prentice-Hall, (1990);
Common Programming Interface Communications Reference,
Fourth Edition, IBM, (1991); Schmidt, Douglas, “Concurrent O-O Network Programming With C++”, C++
World,
1994; and Bach, Maurice J.,
The Design of the Unix Operating System,
Prentice-Hall, (1986).
Various problems exists, however, in managing and controlling these event notifications, especially as the number of intercommunicating objects and as the number of events which need to be communicated increase. These problems are especially acute when the objects are not included within the same application, when the objects are not executing within the same address space or when the objects are not even on the same computer. For example, an object included within a personnel system must provide event notification to another object which is included within an accounting system.
These types of systems can be described in terms of object models, functional models and dynamic models as discussed by James Rumbaugh et al. in the book
Object
-
Oriented Modeling and Design
published in 1991 by Prentice-Hall (the “OOMD”) which is incorporated by reference in its entirety. According to the book OOMD, an object model of a system describes the object types which comprise the system and also shows the relationships between the object types. A functional model of the system shows the processes and data structures of the system and the flow of data therebetween but does not indicate the sequence of processing. The dynamic model of the system does show the sequence of processing of the system. That sequencing is shown primarily as transitions of the object types from one state to another.
The object types used to describe the system using the methodology set forth in the book OOMD include associated data structures and behaviors (or operations). Instantiations of an object type are referred to as objects or object instances. Instantiations of the data structures and behaviors associated with an object type are referred to as attributes and methods, respectively. Execution of the methods associated with a behavior or generation of an event can transition the associated object instances from one state to another. Instantiations of object types, data structures and behaviors occur, in general, when an application requests services from the system.
Thus, what is needed is a method and system for providing managed, controlled event notification between a plurality of software application program objects.
SUMMARY OF THE INVENTION
The present invention is a method and system which provide event notification between a first software application program object and a second software application program object which includes two or more states where the event is associated with a transition of the second application program object from one state to another state.
The invention includes a first means for providing a set of news types associated with one or more event types, each of which describes an event which occurs within or under control of the second application program object during the transition of the second application program object from one state to another state.
The present invention also includes a second means for generating a set of interests, each of which associates the first application program object with one of the news types included in the set of news types.
The first means is also operable to generate, in response to the transition of the second application program object from one state to another, a news object describing the event of one of the event types associated with the transition of the second application program object from one state to another.
The present invention further includes a third means for associating the first application program object with a dispatcher and for dispatching the news object to the first application program object using the dispatcher in accordance with the interest of the first application program object in the news type associated with the event described by the news object thus providing notification of the event to the first application program object.
REFERENCES:
patent: 5133075 (1992-07-01), Risch
patent: 5237684 (1993-08-01), Record et al.
patent: 5475843 (1995-12-01), Halviatti et al.
patent: 5504896 (1996-04-01), Schell et al.
patent: 5652888 (1997-07-01), Burgess
patent: 5870605 (1999-02-01), Bracho et al.
SOMobjects Developer Toolkit Users Guide version 2.0, IBM, p. 12-1—12-8, Jun. 1993.*
H. Ossher, Events as Operations: IBM OOTIS/PCTE Object Event Notification Service Revised Proposal, OMG TC Document May 6, 1993.*
D. Ford, “Association in C++”, Dr. Dobb's Journal, pp. 1-8, Aug. 1994.*
“SOMobjects Base Toolkit Users Guide”, Version 2.0 (2nd Edition), Jan. 1994, US, pp. 9-1—9-8.
“Portable Object-Oriented Event Manager,” IBM Technical Disclosure Bulletin, vol. 37, No. 6B, Jun. 1994, New York, US, pp. 553-555.
S. Menon, et al., “Asynchronous Event Handling In Distributed Object-Based Systems”, Proceedings of the 13th International Conference on Distributed Computing Systems, May 1993, Pennsylvania, USA, pp. 383-390.
“Event Notification Mechanism”, IBM Technical Disclosure Bulletin, vol. 36, No. 4, Apr. 1993,, New York, US, pp. 523-526.
Hall, et al., “Window Sockets—An Open Interface for Network Programming under Microsoft® Windows™”, Version 1.1, Jan. 20, 1993, pp. 1-130.
Hall, Martin, “A Guide to Window Sockets”, Jun. 1993, pp. 1-17.
Birze Brigitte B.
Hager Delmar G.
Traughber Thomas J.
Baker & Botts L.L.P.
Computer Associates Think Inc.
Lao Sue
LandOfFree
Method and system for event notification between software... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method and system for event notification between software..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and system for event notification between software... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3011598