Sending a view event, and a request event having a class name and a method name

• US 6,748,570 B1
• Filed: 10/28/1999
• Issued: 06/08/2004
• Est. Priority Date: 08/03/1999
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bahrs, Peter C., Feigenbaum, Barry Alan, Sundberg, Sean Michael, Modh, Manish Mahesh, Woolfrey, John Allen Hubert, Chancey, Raphael Poole
• Primary Examiner(s): Hong, Stephen S.
• Assistant Examiner(s): Paula, Cesar B
• Application Number:
  US09/429,592
• Time in Patent Office: 1,685 Days
• Field of Search: 715/526, 345/749, 345/760, 345/764, 717/108, 717/116, 717/118
• US Class Current: 715/210
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

A method and apparatus for a data processing system for accessing classes and methods in an object oriented system. Responsive to receiving a selected user input to a container, a view event is sent from a view controller to an application mediator. The view event identifies an action taken to generate the selected user input. A request is selectively generated based on the view event, wherein the request event includes a major code identifying a class name as a destination and a minor code identifying a method name a function to be invoked. The request event is sent to a transporter. The transporter acts as a router to send the request event to an appropriate destination object from a plurality of destination objects. Responsive to receiving the request event at the transporter, the request event is sent to a destination object within a plurality of destination objects based in the class name. The destination object formats the request event into a form recognizable by the destination associated with the destination object. The destination may be located on a remote data processing system. The request event is used to access the class or method identified in the request event. The access may be, for example, an invocation of the method.

Claims

1. A process in a data processing system for processing events in an object oriented system, the method comprising the data processing system implemented steps of:

responsive to receiving a selected user input to a container, sending a view event from a view controller to an application mediator, wherein the view event identifies an action to be taken to generate the selected user input;

selectively generating a request event base on the view event, wherein the request event includes a major code identifying a class name as a destination and a minor code identifying a method name of a function to be invoked; and

sending the request event to a transporter; and

responsive to receiving the request event at the transporter, sending the request event to a destination object within a plurality of destination objects based on in the class name.

2. The process of claim 1, wherein the action is a pressing of a button displayed in the container.

3. The process of claim 1, wherein each of the plurality of destination objects is associated with a destination and wherein each or the plurality of destination objects translates the request event into a format recognizable by the destination.

4. The process of claim 3, wherein the plurality of destinations is a plurality of applications located on a remote data processing system having an ability to communicate with the data processing system.

5. The process of claim 4, wherein the request event is used to invoke the method at the destination.

6. The process of claim 1, wherein the request event includes data in a form of parameters for the method.

7. The process of claim 4, wherein the request event is used to alter a method at the destination.

8. The process for claim 4, wherein the request is event is used to access a class located at the destination.

9. A data processing system for processing events in an object oriented system, the data processing system comprising:

first sending means, responsive to receiving the selected user input to a container, for sending a view event from a view controller to an application mediator, wherein the view event identifies an action to be taken to generate the selected user input;

generating means for selectively generating a request event based on the view event, wherein the request event includes a major code identifying a class name as a destination and a minor code identifying a method name of a function to be invoked;

second sending means for sending the request event to a transporter; and

third sending means, responsive to receiving the request event at the transporter, for sending the request event to a destination object within a plurality of destination objects based on the class name.

10. The data processing system of claim 9, wherein the action is a pressing of a button displayed in the container.

11. The data processing system of claim 9, wherein each of the plurality of destination objects is associated with a destination and wherein each of the plurality of destination objects translates the request event into a format recognizable by the destination.

12. The data processing system of claim 11, wherein the plurality of destinations is a plurality of applications located on a remote data processing system having an ability to communicate with the data processing system.

13. The data processing system of claim 12, wherein the request event is used to invoke the data system at the destination.

14. The data processing system of claim 9, wherein the request event includes data in a form of parameters for the data processing system.

15. The data processing system of claim 12, wherein the request event is used to alter a data processing system at the destination.

16. The data processing system for claim 12, wherein the request event is used to access a class located at the destination.

17. A computer program product in a computer readable medium for processing events in an object oriented system, the computer program product comprising:

first instructions, responsive to receiving a selected user input to a container, for sending a view event from a view controller to an application mediator, wherein the view event identifies an action to be taken to generate the selected user input;

second instructions for selectively generating a request event based on the view event, wherein the request event includes a major code identifying a class name as a destination and a minor code identifying a method name of a function to be invoked;

third instructions for sending the request event to a transporter; and

fourth instructions, responsive to receiving the request event at the transporter, for sending the request event to it destination object within a plurality of destination objects based on its the class name.