Feature #580
open
The more complex methods should be (re)moved from DcmSCU
0%
Description
The DcmSCU class currently contains some more complex methods handling e.g. the (complex) C-GET protocol.
I would suggest that DcmSCU focuses on the (simple) base functionality and leaves others to derived classes.
The same approach has been taken for the C-STORE protocol, where DcmStorageSCU contains the storage-specific code.
Updated by Michael Onken almost 12 years ago
In my opinion a minimal implementation of each DIMSE protocol should be inside the class, so that the normal user does not have to care about too many details, gets an easy example of how implementation works, and may re-use the functions existing from the derived classes. That does not mean that particular extra functionality (e.g. storing files received via C-STORE) could not be removed from the class, though I do not think that is ok as a little example, aside the full implementation offered by the DCMTK class DcmStorageSCP.
At least we should make sure in the future that the class is not overloaded but stays slim.
Updated by Marco Eichelberg over 8 years ago
- Target version changed from 3.6.2 to 3.6.3
Updated by Jan Schlamelcher over 7 years ago
- Target version changed from 3.6.3 to 3.6.6