Sending and Receiving Messages with ISCL
Once an ISCL connection has been established, the client and the server are ready to start transferring messages and data. The data transferred may be secured or unsecured. To send unsecured messages, the user should use the SendNonSecureISCL method. The two events NetNonSecureSendISCL and NetNonSecureReceivedISCL are triggered when non-secure mode data has been either sent or received, repectively.
The SetMaxMessageLengthISCL method sets the maximum message length that can be processed.
For information about confidentiality and data integrity associated with sending secured messages, refer to Adding ISCL Security to a DICOM Connection.
Since encryption modes, message authentication codes, authorization data and message length must all match between a sender and a receiver, occasionally, a sender will send a message that is not received properly by the receiver. When this happens, the receiver, not the sender, can get information about the problems that caused the failure. LEADTOOLS provides the following methods to help the user locate the cause of the problem:
GetPeerRequestedMessageLengthISCL
In addition, when errors occur, the GetErrorSecure and GetStatusISCL can be used to help determine the location of the problem.