Delegate used for the AssociationReleasedEvent event.

This class implements a MessageIterator descendant that handles each association in a different sub DicomThread. Multiple associations may be handled concurrently: when a sub DicomThread accepts an association, this object almost immediately starts a new sub DicomThread that starts listening to the same port. An instance of this class constructed from outside the HLI interface only contains an overview of all started sub DicomThreads in the corresponding results files. A user of this class outside the HLI interface is only concerned with creating an object of this class, calling the correct Initialize method, set the correct options, add MessageHandlers and calling the Start method.

Represents a single thread in which Dicom communication may be tested.

Summary description for DicomThreadOptions.

This abstract class contains the base functionality to implement a DicomThread that, once started, will do things when triggered from the outside. The mechanism used for triggering is calling the Trigger method. The abstract ProcessTrigger method needs to be overriden to determine what needs to be done when this object received a trigger.

Summary description for InboundDicomMessageFilter.

Summary description for InboundDicomMessageFilterSetAttribute.

A descendant of this class is used in combination with a MessageIterator to handle specific Messages that are received by the MessageIterator. An instance of this class will typically implement sending one or more messages as a reaction on specific received message. This class should normally not be concerned with control of flow e.g. like accepting/rejecting an association.

This class represents a framework to loop through received messages and react on these. How to react on messsages may both be implemented by a descendant of this class and by attached MessageHandlers. This class makes it easier to implements SCP's. Typical behaviour that is implemented in a descendant of this class and not in a MessageHandler is control of flow (e.g. determining when to stop listening for new messages, handling the A-ASSOCIATE-RQ, ...). Advantages of using this class instead of looping through received messages in your own classes: - Single way to loop through received messages resulting in more code resembling each other and avoiding code duplication. - More easier to re-use code: MessageHandlers may be used in more then one MessageIteraror descendant. - "Simpel" MessageHandlers may be combined to implement more complex behaviour in a MessageIterator descendant they are attached to.

Delegate used for the MessageReceivedEvent event.

Summary description for OutboundDicomMessageFilter.

Summary description for OutboundDicomMessageFilterSetAttribute.

Summary description for SCP.

This class implements basic functionality for a SCU that is executed in a seperate thread. It is controlled by calling the available Trigger... methods.

Delegate used for the SendingMessageEvent event.