Base class implementation for ports.
Class InputPortProxy is a class that represents to an outer container the functionality of an input port on an internal port owner. This can be used to expose the externally-visible ports from a network of blocks that is being represented as one container-level block.
Class OutputPortProxy is a class that represents to an outer container the functionality of a port on an internal port owner. This can be used to expose the externally-visible ports from a network of blocks that is being represented as one container-level block.
Class PortManagementFacade provides one object from which the managers for all of a group of ports owned by one owner can be obtained. It is a convenience class.
Class PortManager is an abstract class that sets up some of the basic functionality of both input port managers and output port managers.
Contains and provides IPort objects based on keys. PortOwner objects (those which implement IPortOwner) will typically (though not necessarily) contain one of these.
A simple implementation of input port. A data arrival handler may be defined to react to data that has been pushed from its peer - if none is provided, then it cannot accept pushed data, (i.e. can only pull data from its peer at the request of its owner.)
A simple implementation of output port. A data provision handler may be defined to react to a data take request from its peer - if none is provided, then it cannot accept a data take request, (i.e. it can only provide data as a push, driven by the port owner.) A similar handler, with the same conditions, is provided for handling a 'peek' request. If no data provision handler has been provided, either request will return null.
IInputPort is the portion of an InputPort that is intended to be visible and accessible from outside the scope of its owner.
IOutputPort is the portion of an output port that is intended to be visible and accessible from outside the scope of its owner.
This interface specifies the methods common to all types of ports, that are visible to objects other than the owner of the port.
Interface IPortChannelInfo specifies information about what travels on the port, and in what direction. Examples might be "Input" or "Output", or maybe "Control", "Kanban", etc.
An interface describing the events that are fired by all IPort objects.
Interface implemented by any object that exposes ports.
This interface is implemented by any object that can choose ports. It is useful in constructing an autonomous route navigator, route strategy object, or transportation manager.
An interface implemented by a PortSet. Permits indexing to a port by key.
Implemented by a method designed to respond to the arrival of data on a port.
Implemented by a method designed to provide data on an external entity's requesting it from a port.
This is implemented by a method that will be paying attention to a port. PortData events include those occurring when data is presented to a port, accepted by a port, or rejected by a port.
This is the signature of a listener to a port. PortEvents are fired when data becomes available on a port, when a port has just been pulled from or pushed to, or when someone has tried to pull from an empty port.
This delegate receives the object passed in on a port and the set of choices to which it can be passed.