The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Oct. 13, 1998
Filed:
May. 30, 1997
William Noble, South Lyon, MI (US);
Michael Knight, Northville, MI (US);
Karen Nelson-Katt, West Bloomfield, MI (US);
Compuware Corporation, Farmington Hills, MI (US);
Abstract
An object-oriented framework is used to build cooperative objects. Objects can span processes on different machines connected by a network. The objects are used to build distributed or cooperative applications which execute in multiple environments without having to write significant additional code to enable such functionality. Each cooperative object has two parts: an agent object and a server object. Requests for services are made to agent objects by the application program (via an asynchronous interface) as if they were local objects. The server object performs the requested service in the server process, possibly using other server objects or systems (e.g., DB/2), and returns the result to the associated agent object. A Distributor and Dispatcher object in each process handle communication between agent and server objects. The Distributor receives all incoming messages and routes them to the appropriate objects in the process. The Dispatcher is used for sending messages to other objects. Agent and server objects use framework methods SendMessage and HandleMessage to send/receive messages to/from other objects. Message data is converted to account for parameter types in different processing environments (e.g., byte-swapping and ASCII to EBCDIC). Upon receipt of a message, the Distributor automatically calls the HandleMessage method of the receiving object. The object then processes the request according to the user-defined implementation of the HandleMessage method and, in the client process, notifies the application of the completion of a request via a Callback method.