System of reusable software parts for distributing event flows and methods of use

In a software system, said software system having a plurality of objects, a container object comprising:

• a first memory for keeping reference to at least a first object of arbitrary object class;
• a section of program code causing said first memory to be modified so that it will contain a first reference to a second object;
• a section of program code accessing a data structure and determining that at least a first connection needs to be established between said second object and at least a third object;
• a section of program code causing said first connection to be established.

In a software system, said software system having a plurality of objects, a container object comprising:

• a memory for keeping at least one reference to a contained object of arbitrary class;
• a connection point for receiving requests to modify the set of contained objects;
• at least one virtual connection point that accepts at least a first connection to be established to said contained object, said acceptance occurring before said contained object is added to said contained object;
• a section of program code that establishes said first connection when said contained object is added to said container object.

In a software system, said software system having a plurality of objects, a container object comprising:

• a first memory for keeping at least one reference to a contained object of arbitrary class;
• a connection point for receiving requests to modify the set of contained objects;
• at least one virtual property that accepts the value to be set in a first property on said contained object, said virtual property being capable of accepting values of a plurality of data types;
• a section of program code that sets said first property on said contained object to said accepted value when said contained object is added to said contained object.

A container object in a software system, said software system having a plurality of objects, said software system having means for requesting operations over an object, said container object comprising:

• means for holding a plurality of contained objects;
• means for changing the set of said contained objects programmatically;
• means for identifying each object of said contained objects by a separate, unique identifier for each object;
• means of handling requests for operations over any object of said contained objects wherein said identifier is used to determine which object of said contained objects should handle the request.

A method for caching and propagating property values to a dynamic set of objects in a software system, said software system having a plurality of objects, each of said objects having a plurality of properties, each said property having a value and an identifier, said method comprising the steps of:

• accepting a first request to modify the value of a first property on behalf of said dynamic set of objects as if said dynamic set of objects were one object;
• storing said value and identifier of said first property in a first data storage;
• retrieving said value and identifier of said first property from said first data storage;
• issuing a request to modify the value of said first property on a first object of said dynamic set of objects, using said value and identifier retrieved from said first data storage.

A method for caching and propagating outgoing connections of a dynamic set of objects in a software system, said software system having a plurality of objects, said software system having means for establishing connections between said objects, said connections providing means for a first connected object to make outgoing calls to a second connected object, said method comprising the steps of:

• accepting the request to establish a first outgoing connection between said dynamic set of objects and a first object, as if said dynamic set of objects were a single object;
• storing a first data value necessary to effect said first connection in a first data storage;
• retrieving said first data value from said first data storage;
• issuing a request to establish a second connection between a second object of said dynamic set and said first object, using said first data value retrieved from said first data storage.

A container object in a software system, said software system having a plurality of objects, said software system having means of building at least one structure of connected objects, said software system having a first means of describing said structure, said software system providing a second means of enumerating all connections described by said first means, said container being a first object in said structure, said container being connected to at least a second object in said structure, said container comprising:

• means for holding a plurality of contained objects;
• means for changing the set of said contained objects programmatically;
• means for finding a first described connection between said container and said second object;
• means for establishing said first connection between a third object contained in said container and said second object.

A container object in a software system, said software system having a plurality of objects, said container having a first connection to at least one object, said first connection being described in a first data structure, said container comprising:

• means for holding a plurality of contained objects;
• means for changing the set of said contained objects programmatically;
• means for determining a first set of connections to be established for each object added to said set of contained objects based on the set of connections described in said first data structure;
• means for establishing said first set of connections.

A part for distributing events among a plurality of parts, said part comprising:

• a multiple cardinality input,
• a multiple cardinality output,
• means for recording references to parts that are connected to said output
• means for forwarding events received on said input to each of the connected objects to said output.

A part for distributing events and requests between a plurality of other parts, said part comprising:

• a first terminal for receiving calls;
• a second terminal for sending calls out to a first connected part;
• a third terminal for sending calls out to a second connected part;
• means for choosing whether to send the received call through said second terminal or through said third terminal.

A part for distributing events and requests between a plurality of other parts, said part comprising:

• a first terminal for receiving calls;
• a second terminal for sending calls out to a first connected part;
• a third terminal for sending calls out to a second connected part;
• means for choosing whether to first send the received call through said second terminal and then through said third terminal or to first send the received call through said third terminal and then through said second terminal.

A part for distributing events and requests between a plurality of other parts, said part comprising:

• a first terminal for receiving calls;
• a second terminal for sending calls out to a first connected part;
• a third terminal for sending calls out to a second connected part;
• means for sending a first received call as a first call to said second terminal and then, based on value returned from said first call, choose whether or not to send said first received call as a second call to said third terminal.

A part in a software system, said part comprising:

• a first terminal for receiving calls;
• a second terminal for sending calls out to a first connected part;
• a third terminal for receiving a pulse call;
• a memory for storing call information received from said first terminal;
• a section of program code that is executed when said part receives said pulse calls, said section retrieving said call information from said memory and sending a call out to said second terminal.

A part in a software system, said part comprising:

• a first terminal for receiving calls;
• a second terminal for sending calls out to first connected part;
• a memory for storing call information received from said first terminal;
• a means for obtaining execution context;
• a section of program code that is executed in said execution context, said section retrieving said call information from said memory and sending a call out to said second terminal.

A part in a software system, said part comprising:

• a first terminal for receiving an incoming request;
• a second terminal for sending out an outgoing request;
• a third terminal for receiving a request completion indication;
• a synchronization object for blocking the thread in which said incoming request was received until said request completion indication is received.

A part in a software system, said part comprising:

• an input terminal for receiving calls of a first type and sending calls of said first type;
• an output terminal for receiving calls of a second type and sending calls of said second type;
• means for converting calls of said first type to calls of said second type;
• means for converting calls of said second type to calls of said first type.

A part in a software system, said part comprising:

• a first terminal for receiving calls;
• a second terminal for sending out calls received on said first terminal;
• a first property for configuring a first value;
• a third terminal for sending out notification calls whenever a call sent out said second terminal returns a second value that matches said first value.

A part in a software system, said part comprising:

• a first terminal for receiving a first call;
• a second terminal for sending out said first call;
• means for extracting data from said first call;
• means for formatting said extracted data as a first text;
• means for sending out said first text.

A part in a software system, said part comprising:

• a first terminal for receiving calls;
• a second terminal for sending out calls received on said first terminal;
• a third terminal for sending out requests to create new parts;
• means for selecting calls received on said first terminal for which said part sends out requests on said third terminal.

A method for designing access to a hardware component in a component-based software system, said method comprising the steps of:

• designating a first software component for receiving interrupts from said hardware component;
• designating a at least a second software component for accessing input and output ports of said hardware component;
• designating a third software component for handling interrupts received by said first software component;
• designating a fourth software component for manipulating said hardware component;
• connecting said first software component to said third software component,,
• connecting said second software component to said fourth software component.

A method for designing software system in which system at least a first object is created arbitrarily earlier than a second object and said second object is automatically connected to at least said first object, said method comprising the steps of:

• creating said first object;
• creating a first container object capable of holding at least one other object of arbitrary object class;
• defining at least a first template connection between said first object and said first container object;
• creating said second object;
• connecting said second object to said first object using said first template connection in which template said first container object is replaced with said second object.