Actions
Feature #1071
open
DcmSCU does not always allow to access the DIMSE Status Code returned in the response Command Set
Status:
New
Priority:
Normal
Assignee:
-
Category:
Library
Target version:
-
Start date:
2023-04-03
Due date:
% Done:
0%
Estimated time:
Module:
dcmnet
Operating System:
Compiler:
Description
DcmSCU currently handles many details of the DICOM network protocol completely internally and does not even allow users of this class to access fundamental information.
For example the sendECHORequest() method handles the entire exchange request and response Command Set between the communication peers, but neither checks for nor allows one to access the DIMSE Status Code.
- By extending all sendXXXRequest() methods that receive the response Command Set by returning the DIMSE Status Code in a optional output parameter "rspStatusCode" (see e.g. sendACTIONRequest()).
- By implementing virtual methods like handleReceivedDIMSECommand() or notifiyDIMSECommandReceived(), which can be overwritten in derived classes and allow for accessing the DIMSE Status Code.
- By implementing virtual methods that are specific to the various DIMSE Messages, e.g. handleECHOResponse(), handleSTOREResponse() like it is done for handleFINDResponse() and handleMOVEResponse().
The above list does not claim to be exhaustive. It may also be useful to implement more than one of the described approach to be more flexible.
No data to display
Actions