====== Plans for Storage Commitment Server ======

**__General__**
  * Standalone command line application.
  * Could be integrated with storescp and dcmqrscp (simple image archive).
  * Should be able to receive N-ACTION-RQ and respond with N-ACTION-RSP.
  * It should be able to support sending N-EVENT-REPORT both on the same association or on a different association.
  * Permit single and multi-process mode (i.e. start new process for each incoming association).

__**Configuration Options**__
  * It should be configured to scan a directory to search for files to be committed or to search in a database file (INDEX.DAT).
  * It should be configured to a listening port number. 
  * It could be configured to send N-EVENT-REPORT using one of the two options (1: use same association ; 2: use a different association).
  * Select either single or multi-process mode

__**N-ACTION**__
  * Once the storage commmitment server received N-ACTION-REQUEST, it should respond with N-ACTION-RSP with a status success indicating that the server is now processing the stored files to be committed. And it should respond with N-ACTION-RSP with status failed indicating that it failed to process the request.
  * Storage commitment SCU is free to release the association after receiving N-ACTION-RSP. So, SCP shall support sending N-EVENT-REPORT on a different association.


__**N-EVENT-REPORT**__
  * SCP should respond with the same transaction uid used in the initiating request (N-ACTION-RQ). 
  * Event ID equals 1 means all files are successfully committed. 
  * Event ID equals to 2 means some files failure exists. 
  * The dicom dataset should contain the transaction uid, the list of success sop class/instance uid and a list of failed sop class/instance uids (if any).