Agent-based multithreading application programming interface

• US 5,421,013 A
• Filed: 07/08/1993
• Issued: 05/30/1995
• Est. Priority Date: 07/08/1993
• Status: Expired due to Term

• Current Assignee: Stafanpolus KG Limited Liability Company
• Original Assignee: Park City Group Incorporated
• Inventors: Smith, Curtis A.
• Primary Examiner(s): Kriess, Kevin A.
• Assistant Examiner(s): COURTENAY III, ST JOHN
• Application Number:
  US08/088,825
• Time in Patent Office: 691 Days
• Field of Search: 395/700, 395/650
• US Class Current: 718/107
• CPC Class Codes: G06F 9/4484 Executing subprograms
• CPC Class Codes: G06F 9/4488 Object-oriented
• CPC Class Codes: G06F 9/4881 Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues

Abstract

An application programming interface facilitates development of portable, multithreaded application programs. An application is a collection of instances of agent classes. Agent classes are organized in class hierarchies because new subclass agents may be derived from existing base class agents. Each agent class has its own message dispatching function; this allows the application programmer to alter the message passing framework provided by the application programming interface. Each agent instance within the program is independent because it is a sub-process aware only of its own data and context. Multithreading is provided by the application programming interface which contains a master dispatcher process non-preemptively allocating time to individual agents. Therefore, an application'"'"'s multithreading capability is independent of the platform'"'"'s operating system. In addition, a thread of execution may be split when the currently activated agent activates the master dispatcher. The application programming interface mediates between the system resources and the application, and maps the user interface of the application to the platform'"'"'s chosen user interface. Therefore, the application and its user interface are portable.

Claims

1. A system for implementing an agent-based application program on a computer, comprising:

a processor;

an input device coupled to the processor, for accepting input;

an output device coupled to the processor, for providing output;

memory unit coupled to the processor, for storing data and program instructions;

an operating system, stored in the memory and managing a plurality of processes created by execution of program instructions in the memory unit by the processor;

and at least one agency application unit coupled to the processor and managing a plurality of agents stored in the memory unit, and including;

a master dispatcher coupled to the plurality of agents, for receiving from, and sending messages to the agents, and responsive to all agents being inactive, selecting an agent and activating the selected agent;

the plurality of agents, each agent responsive to being activated by the master dispatcher, for executing an application function, each agent comprising;

a message dispatcher for receiving a signal from the master dispatcher activating the agent, and for dispatching at least one message providing for execution of the application function;

at least one message queue, for receiving and storing at least one message from the master dispatcher and from other sources, and operatively coupled to the message dispatcher and responsive to the agent being active, for passing at least one stored message to the message dispatcher for dispatching; and

a message processor operatively coupled to the message dispatcher and receiving a dispatched message, for executing the application function of the received message.

2. The system of claim 1, wherein each agent, responsive to completing at least one application function, designates itself as inactive.

3. The system of claim 1, wherein:

the agency application unit further includes an agent list coupled to the master dispatcher; and

the master dispatcher selects a first agent from the agent list, and activates the first agent by invoking the first agent'"'"'s message dispatcher, the first agent executing selected processes with the processor, such that the master dispatcher waits to select or activate a second agent until the first agent has designated itself inactive.

4. The system of claim 1, wherein the message processor of a first agents calls the master dispatcher of the agency application unit, the master dispatcher suspending the first agent, selecting at least one second agent, and activating the second agent, and unsuspending the first agent when the second agent designates itself inactive.

5. The system of claim 1, wherein the message dispatcher of an activated agent retrieves a message stored in a message queue of a deactivated agent, and passes the retrieved message to the message processor of the activated agent for executing the application function of the retrieved message.

6. The system of claim 1, wherein the message dispatcher of an activated agent stores a message in a message queue of a deactivated agent.

7. The system of claim 1, wherein there is a base agent class, and a plurality of agent subclasses derived from the base agent class, and wherein there is an agent list, each agent in the agent list being an instance of one agent subclass, wherein:

the message processor of an activated agent determines whether a received message applies to the agent subclass of which the activated agent is an instance;

responsive to the received message applying to the agent subclass, executing the application function of the received message; and

responsive to the received message not applying to the agent subclass, calling a base class message processor, the base class message processor executing the application function of the received message.

8. The system of claim 1, wherein the message dispatcher dispatches messages from the message queue to the message processor until the message queue is empty.

9. The system of claim 1, wherein the message dispatcher dispatches messages from the message queue to the message processor until the agent signals that it is yielding its time, the message dispatcher deactivating the agent.

10. The system of claim 1, wherein the message dispatcher creates a process for execution by the processor in addition to any application functions executed by the message processor.

11. The system of claim 1, wherein the master dispatcher preemptively activates a selected agent.

12. A computer-implemented process for controlling agent operation in an agent-based application program having a plurality of agents, comprising the steps of:

responsive to all agents being inactive, performing the substeps of;

selecting an agent; and

activating the selected agent;

responsive to at least one agent being active, the agent performing the operations of;

receiving at least one message from a source external to the agent, or from the agent itself, the message providing for the execution of an application function;

storing received messages in a message queue coupled to the agent;

determining if the message queue contains at least one message;

responsive to the message queue containing at least one message,

removing a message from the message queue and performing an application function according to the message; and

responsive to the message queue being empty, designating the agent as inactive.

13. The method of claim 12, wherein an agent further performs the operations of:

selecting one of a plurality of messages queues, each message queue for storing a plurality of messages; and

storing a received message in the selected message queue.

14. The method of claim 12, wherein the step of receiving at least one message further comprises the substeps of:

retrieving a message stored in a message queue of a deactivated agent.

15. The method of claim 12, further comprising the operation of:

storing a message in a message queue of a deactivated agent.

16. The method of claim 12, wherein the steps of removing the message from the message queue and performing the application function according to the message are performed until the message queue is empty.

17. The method of claim 12, wherein the steps of removing the message from the message queue and performing the application function according to the message are performed until the agent yields its time.

18. The method of claim 12, wherein the step of activating the selected agent is performed preemptively.

19. The method of claim 12, further comprising the step of the message dispatcher of an activated agent creating a process for execution by a processor in addition to any application function executed by the message processor.